From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on061c.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe1f::61c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id E66DF821F9 for ; Fri, 3 Mar 2017 03:30:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Mt2c2WlfJK4E/4tvQ8rMOcUfzCEQHqp5og43+WVjRfM=; b=LXDt/BLAzqouFHcBmOGCNkSAmCwfrn+Ubfb5xCeVr5sNbrSxMm21FuhF3QJX4tF0/4/XVy0mkJ3HRBbkek2q7Nu+g9l5NLbsd63RtP6oVK3VD0OVJtpooiNTPUa/a2m4+XfdhUihGTzS6jpzF27trp6Wf8dFhiOb99s4A2LT+bs= Received: from DB5PR04MB0998.eurprd04.prod.outlook.com (10.161.199.12) by DB5PR04MB0999.eurprd04.prod.outlook.com (10.161.199.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12; Fri, 3 Mar 2017 11:30:10 +0000 Received: from DB5PR04MB0998.eurprd04.prod.outlook.com ([fe80::3825:8aa3:e6e6:2c5f]) by DB5PR04MB0998.eurprd04.prod.outlook.com ([fe80::3825:8aa3:e6e6:2c5f%17]) with mapi id 15.01.0947.012; Fri, 3 Mar 2017 11:30:10 +0000 From: Meenakshi Aggarwal To: "edk2-devel@lists.01.org" Thread-Topic: soc specific fixups in dtb Thread-Index: AdKUDpWuTq5kWAZCS6+/s6FRJZy1xg== Date: Fri, 3 Mar 2017 11:30:10 +0000 Message-ID: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ml01.01.org; dkim=none (message not signed) header.d=none;ml01.01.org; dmarc=none action=none header.from=nxp.com; x-originating-ip: [192.88.169.1] x-ms-office365-filtering-correlation-id: f3112d7a-5647-4ac8-b0cc-08d46228a6e4 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:DB5PR04MB0999; x-microsoft-exchange-diagnostics: 1; DB5PR04MB0999; 7:3tg0uuN/Zztt1+JspLwNWYjomtE/Hk9p/C+C1XE4gsNo6XF/fMPxAvM2iYv66Y9aMKCIUnxsRv9/n3jjEGK7wlqfIj9+Y8q+8th1odzKOYKxRXnlT0nTIWAhX7N4yY1ReyZlVqCmY9JWlH+32Qt3qB5yeRY0XU+BfGWvA84GtgNvIDoRZPe5EM3nUCWdxg21QiUoT56h4gPt0kzxTg0NOxLflarNxutwn15f4MpbovTIq/aJZ81W1DpYGOi3wYBFOLJGYdf54Mw4Mpze/IkyvKkh6I3M6ursnypJwwzcDfmaEHvuO8O5ISUSwMKqozDk4hsN+IwDmCIkhUiTi5VWhA== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123560025)(20161123558025)(20161123562025)(20161123564025)(20161123555025)(6072148); SRVR:DB5PR04MB0999; BCL:0; PCL:0; RULEID:; SRVR:DB5PR04MB0999; x-forefront-prvs: 0235CBE7D0 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(39410400002)(39850400002)(39840400002)(53754006)(7696004)(2351001)(8676002)(81166006)(8936002)(5660300001)(92566002)(5250100002)(33656002)(7736002)(3846002)(2900100001)(74316002)(54356999)(305945005)(66066001)(102836003)(6116002)(50986999)(38730400002)(6916009)(9686003)(3280700002)(53936002)(6506006)(110136004)(6436002)(2906002)(3660700001)(99286003)(55016002)(450100001)(86362001)(189998001)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB5PR04MB0999; H:DB5PR04MB0998.eurprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2017 11:30:10.0707 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR04MB0999 Subject: soc specific fixups in dtb X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 11:30:13 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I need to perform some soc specific fixups in dtb binary before passing it = to kernel. And also I want to perform these fixups from efi shell, so that I don't hav= e to set any PCD for fdt device path. I can achieve my purpose by placing a hook in=20 " EmbeddedPkg/Drivers/FdtPlatformDxe/FdtPlatform.c " if (fdt_check_header ((VOID*)(UINTN)FdtBlobBase) !=3D 0 || (UINTN)fdt_totalsize ((VOID*)(UINTN)FdtBlobBase) > FdtBlobSize) { DEBUG ((EFI_D_ERROR, "InstallFdt() - loaded FDT binary image seems cor= rupt\n")); @@ -108,12 +107,13 @@ InstallFdt ( } =20 + FdtCpuSetup((VOID **)&FdtBlobBase, &FdtBlobSize); =20 // // Store the FDT as Runtime Service Data to prevent the Kernel from // overwritting its data. // =20 And calling setfdt -i fs0:fdt.dtb Command from shell. I know this is not a correct way of performing dtb fixups. Is there any alternative to achieve same? Or I need to write my own driver and shell command for performing dtb fixup= s? Thanks, Meenakshi