From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 4AB4521A143C1 for ; Tue, 4 Jul 2017 13:09:13 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 64B2B3B703; Tue, 4 Jul 2017 20:10:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 64B2B3B703 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=lersek@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 64B2B3B703 Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-126.phx2.redhat.com [10.3.116.126]) by smtp.corp.redhat.com (Postfix) with ESMTP id C18C451C91; Tue, 4 Jul 2017 20:10:50 +0000 (UTC) To: Amit kumar , "edk2-devel@lists.01.org" References: From: Laszlo Ersek Message-ID: Date: Tue, 4 Jul 2017 22:10:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Tue, 04 Jul 2017 20:10:51 +0000 (UTC) Subject: Re: writing EDK compatible application. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2017 20:09:13 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 07/04/17 19:20, Amit kumar wrote: > > HI, > > I have written a code (say helloworld program ) using edk2 framework, named the output efi file as BOOTx64.efi and placed it on a removable media in EFI/BOOT/ directory so that the application is listed in one time boot menu. When selected from boot menu it prints "Hello World". > Which works as expected when tested on UEFI 2.3 and above platforms. > But the same code fails to execute on EFI 1.10 platforms. Which i suppose is the problem with application entry point. > Can somebody suggest me a way so that the application entry function can be compatible to both the platform. Even when written according to UEFI 2.5+ Spec ? I don't think you can develop for EFI 1 using edk2 -- unless you use EdkCompatibilityPkg I guess. But, I don't know how much EdkCompatibilityPkg is maintained. Here's some links: https://github.com/tianocore/tianocore.github.io/wiki/EdkCompatibilityPkg https://github.com/tianocore/tianocore.github.io/wiki/EDK The entry point is likely the least of your problems. The library instances pulled in from under MdePkg, MdeModulePkg etc are full of UEFI 2.* dependencies, I'm pretty sure. I would suggest ignoring EFI 1... Thanks Laszlo