From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=yonghong.zhu@intel.com; receiver=edk2-devel@lists.01.org Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3EA1C210C2D63 for ; Thu, 26 Jul 2018 17:59:56 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jul 2018 17:59:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,407,1526367600"; d="scan'208";a="249336854" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga006.fm.intel.com with ESMTP; 26 Jul 2018 17:59:52 -0700 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 26 Jul 2018 17:59:52 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX154.amr.corp.intel.com (10.18.116.70) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 26 Jul 2018 17:59:52 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.100]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.173]) with mapi id 14.03.0319.002; Fri, 27 Jul 2018 08:59:27 +0800 From: "Zhu, Yonghong" To: Tim Lewis , "edk2-devel@lists.01.org" Thread-Topic: [edk2] FFS Alignment and the FDF Specification Thread-Index: AdQlRA9s8HWyRfiOR4+k2YpCN5H++AAAK/vw Date: Fri, 27 Jul 2018 00:59:26 +0000 Message-ID: References: <06fb01d42544$6cbc7180$46355480$@insyde.com> In-Reply-To: <06fb01d42544$6cbc7180$46355480$@insyde.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNmU3MDA0NjUtYzQxYS00MzMxLWIyZGEtNTQxMTVkMzc0MDA4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiRVdhV2sxaDZETTc3aDBpT0g0WENNSU5Xd2ZvMVVQTTNrR29CUGZTNTFJQXQyTjlhNmcwdmd2N2NDcDRlNko2dSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: FFS Alignment and the FDF Specification X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 00:59:56 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Which version of FDF spec you use now ? I remember current we already suppo= rt 16M ffs alignment. FDF spec Version 1.28 have such info "Per PI 1.6 to = extend FFS alignment to 16M". Best Regards, Zhu Yonghong -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Tim = Lewis Sent: Friday, July 27, 2018 8:55 AM To: edk2-devel@lists.01.org Subject: [edk2] FFS Alignment and the FDF Specification Is my understanding correct: the FDF specification only supports a maximum = of 64KB alignment for files (section 2.5.6), but the PI specification suppo= rts (table 7), up to 16MB alignment. Or am I misreading it? Thanks, Tim -----Original Message----- From: edk2-devel On Behalf Of Andrew Fish Sent: Thursday, July 19, 2018 11:26 AM To: Marvin H?user Cc: edk2-devel@lists.01.org Subject: Re: [edk2] Help on AutoGen Files Udit, As Marvin points out the [LibraryClasses] section of the INF file are going= to imply the order of the library constructor calls in the AutoGen Worst case you can demote FpgaInterfaceInit () from being a constructor to = just being a public library function that the other lib can call explicitly= from its constructor. Maybe that is too drastic and you could must move a = function out of FpgaInterfaceInit () and make that function part of the Pub= lic library interface? Thanks, Andrew Fish > On Jul 19, 2018, at 11:14 AM, Marvin H?user=20 > wrote: >=20 > Hey Udit, >=20 > You cannot explicitly influence the order of the calls, but implicitly=20 > via the dependency tree, which means you need to make SerialPortLib depend on y= our LibraryClass instance. > You did not mention which SerialPortLib instance you use, but probably=20 > you need to execute FpgaInterfaceInit() earlier in platform code or fork Serial= PortLib for now. >=20 > Regards, > Marvin >=20 >> -----Original Message----- >> From: edk2-devel On Behalf Of Udit=20 >> Kumar >> Sent: Thursday, July 19, 2018 9:33 AM >> To: edk2-devel@lists.01.org >> Subject: [edk2] Help on AutoGen Files >>=20 >> Hi Experts, >> How I can change the order of initialization in Constructor list of autogen file. >> In my build system, if I look at >> MdeModulePkg/Universal/PCD/Pei/Pcd/DEBUG/AutoGen.c >> Below is function of Library Constructor List >>=20 >> VOID >> EFIAPI >> ProcessLibraryConstructorList ( >> IN EFI_PEI_FILE_HANDLE FileHandle, >> IN CONST EFI_PEI_SERVICES **PeiServices >> ) >> { >> EFI_STATUS Status; >>=20 >> Status =3D BaseDebugLibSerialPortConstructor (); ASSERT_EFI_ERROR=20 >> (Status); >>=20 >> Status =3D PeiServicesTablePointerLibConstructor (FileHandle,=20 >> PeiServices); ASSERT_EFI_ERROR (Status); >>=20 >> Status =3D TimerConstructor (); >> ASSERT_EFI_ERROR (Status); >>=20 >> Status =3D FpgaInterfaceInit (); >> ASSERT_EFI_ERROR (Status); >>=20 >> } >>=20 >>=20 >> My problem is SerialPortConstructor needs frequency, which can be=20 >> retrieved after FpgaInterfaceInit() Therefore, my preferred way for=20 >> this constructor list will be >> FpgaInterfaceInit() followed by BaseDebugLibSerialPortConstructor() >>=20 >> how I can achieve this. >>=20 >>=20 >> Many Thanks >> Udit >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel