From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=210.71.195.42; helo=out02.hibox.biz; envelope-from=tim.lewis@insyde.com; receiver=edk2-devel@lists.01.org Received: from out02.hibox.biz (out02.hibox.biz [210.71.195.42]) (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 AB3B1210C2D64 for ; Thu, 26 Jul 2018 18:09:03 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2C+AADnbVpb/ww0GKxcGgEBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYQxbRIojARfjWoxAYJ7iVGIUIF6CxgLCAGEOgQCAoMZNBgBAgEBAgE?= =?us-ascii?q?BAm0cDIU2AQEBAQIBAQEGAjAcCA0DEAcBAwIGAw0EBAEBAScHGQ4BEQ0JCAIEA?= =?us-ascii?q?RILBYMLBAKBZwMNCA+wURoCiiIFilo/gRGDEoMbAQSHMwKNHy6MLgcCAoF2hB6?= =?us-ascii?q?CZYJMg26IPwOFQYpNh2aBQTgNgUVwUIJpP4FmF4hZhV4fMIEOCAwBjXMBAQ?= X-IronPort-AV: E=Sophos;i="5.51,407,1526313600"; d="scan'208";a="6357867" Received: from unknown (HELO hb3-BKT202.hibox.biz) ([172.24.52.12]) by out02.hibox.biz with ESMTP; 27 Jul 2018 09:09:02 +0800 Received: from unknown (HELO hb3-BKT103.hibox.biz) ([172.24.51.13]) by hb3-BKT202.hibox.biz with ESMTP; 27 Jul 2018 09:09:03 +0800 Received: from unknown (HELO hb3-IN03.hibox.biz) ([172.24.12.13]) by hb3-BKT103.hibox.biz with ESMTP; 27 Jul 2018 09:09:02 +0800 X-Remote-IP: 50.235.79.131 X-Remote-Host: 50-235-79-131-static.hfc.comcastbusiness.net X-SBRS: None X-MID: 14613243 X-Auth-ID: tim.lewis@insyde.com X-EnvelopeFrom: tim.lewis@insyde.com hiBox-Sender: 1 Received: from 50-235-79-131-static.hfc.comcastbusiness.net (HELO TIMSLAPTOP) ([50.235.79.131]) by hb3-IN03.hibox.biz with ESMTP/TLS/AES256-SHA; 27 Jul 2018 09:09:01 +0800 From: "Tim Lewis" To: "'Zhu, Yonghong'" , References: <06fb01d42544$6cbc7180$46355480$@insyde.com> In-Reply-To: Date: Thu, 26 Jul 2018 18:08:57 -0700 Message-ID: <06ff01d42546$677de7b0$3679b710$@insyde.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQGjygYpXcGUSuEHo01neIeGcRgzHAITkSrJpPJbzpA= 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 01:09:05 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-language: en-us 1.28. 2.5.6 says: Alignment - Data (value is one of: 1, 2 4, 8, 16, 32, 64 128, 512, 1K, 2K, 4K, 8K, 16K,32K, 64K) byte aligned The grammar 3.2.1 says: ::= {"Auto"} {"8"} {"16"} {"32"} {"64"} {"128"}{"512"} {"1K"} {"4K"} {"32K"} {"64K"} This is the version from the EDK2 specs page. -----Original Message----- From: edk2-devel On Behalf Of Zhu, Yonghong Sent: Thursday, July 26, 2018 5:59 PM To: Tim Lewis ; edk2-devel@lists.01.org Subject: Re: [edk2] FFS Alignment and the FDF Specification Which version of FDF spec you use now ? I remember current we already support 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 supports (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 Public library interface? Thanks, Andrew Fish > On Jul 19, 2018, at 11:14 AM, Marvin H?user > wrote: > > Hey Udit, > > You cannot explicitly influence the order of the calls, but implicitly > via the dependency tree, which means you need to make SerialPortLib depend on your LibraryClass instance. > You did not mention which SerialPortLib instance you use, but probably > you need to execute FpgaInterfaceInit() earlier in platform code or fork SerialPortLib for now. > > Regards, > Marvin > >> -----Original Message----- >> From: edk2-devel On Behalf Of Udit >> Kumar >> Sent: Thursday, July 19, 2018 9:33 AM >> To: edk2-devel@lists.01.org >> Subject: [edk2] Help on AutoGen Files >> >> 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 >> >> VOID >> EFIAPI >> ProcessLibraryConstructorList ( >> IN EFI_PEI_FILE_HANDLE FileHandle, >> IN CONST EFI_PEI_SERVICES **PeiServices >> ) >> { >> EFI_STATUS Status; >> >> Status = BaseDebugLibSerialPortConstructor (); ASSERT_EFI_ERROR >> (Status); >> >> Status = PeiServicesTablePointerLibConstructor (FileHandle, >> PeiServices); ASSERT_EFI_ERROR (Status); >> >> Status = TimerConstructor (); >> ASSERT_EFI_ERROR (Status); >> >> Status = FpgaInterfaceInit (); >> ASSERT_EFI_ERROR (Status); >> >> } >> >> >> My problem is SerialPortConstructor needs frequency, which can be >> retrieved after FpgaInterfaceInit() Therefore, my preferred way for >> this constructor list will be >> FpgaInterfaceInit() followed by BaseDebugLibSerialPortConstructor() >> >> how I can achieve this. >> >> >> 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 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel