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 A05431A1E3E for ; Tue, 18 Oct 2016 10:41:00 -0700 (PDT) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 35F6BC062C95; Tue, 18 Oct 2016 17:41:00 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-72.phx2.redhat.com [10.3.116.72]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u9IHewxK015479; Tue, 18 Oct 2016 13:40:59 -0400 To: Saqib Khan References: Cc: edk2-devel@ml01.01.org From: Laszlo Ersek Message-ID: <4e344fbc-5d83-c963-2867-461d40832c8d@redhat.com> Date: Tue, 18 Oct 2016 19:40:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Tue, 18 Oct 2016 17:41:00 +0000 (UTC) Subject: Re: How to get BBS_BBS_DEVICE_PATH from BOOTXXXX variable 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: Tue, 18 Oct 2016 17:41:00 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 10/18/16 19:18, Saqib Khan wrote: > Hi, > I can not find structure of BOOTXXXX variable, Can any one help how to > extract device path from BOOTXXXX variable. In UEFI-related questions, the UEFI specification has a fair chance to provide useful information. Please refer to "3.1.3 Load Options" in the UEFI v2.6 spec, available for download from . Locating the matching structure definition in the edk2 tree is left as an exercise to the reader ;) Laszlo