From: Rod Smith <rodsmith@rodsbooks.com>
To: edk2-devel@lists.01.org, saqib.khan2011@gmail.com
Subject: Re: Help Required legacy booting from an EFI
Date: Tue, 20 Sep 2016 15:41:09 -0400 [thread overview]
Message-ID: <1ed8f5d6-7937-b723-086a-c09afef14d6e@rodsbooks.com> (raw)
In-Reply-To: <CAF=YJJ-022aX7QnwOB3f1Yo_VZUXa44OHbDyJY59aps=+2Bz1A@mail.gmail.com>
On 09/20/2016 02:38 PM, Saqib Khan wrote:
>
> Booting using BBS is my option,i was already looking for this and I have
> attempted to modify EFIBootManagerMenuApp to work with legacy boot used ().
>
> I have system with CSM support so essentially i will be doing all my work
> on physical system not on virtual machine.
>
> The detail you provided about BBS device path and then adding it to boot
> menu is abstract for me .if you can detail this procedure a bit it will be
> helpful, if required I can share the code snippet with you
You may want to look at the relevant bits of code in my rEFInd boot manager:
https://sourceforge.net/projects/refind/
In particular, look at the functions in EfiLib/legacy.c and
refind/legacy.c. One big caveat is that rEFInd includes TWO code paths
for launching BIOS-mode boot loaders -- one it inherits from its
predecessor project, rEFIt, and works only on Macs; and the other was
contributed by John Bressler and works only on UEFI-based PCs. Since I
wrote neither, I can't offer a lot of insight into how either one works.
(The Mac side, in particular, is pretty mysterious to me.) There may be
a better way to do it than what rEFInd does, but at least rEFInd's code
does work. Thus, if you need a concrete example, the rEFInd code might
be helpful.
--
Rod Smith
rodsmith@rodsbooks.com
http://www.rodsbooks.com
prev parent reply other threads:[~2016-09-20 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 15:00 Help Required legacy booting from an EFI Saqib Khan
2016-09-19 17:49 ` Laszlo Ersek
2016-09-20 18:38 ` Saqib Khan
2016-09-20 19:13 ` Laszlo Ersek
2016-09-22 11:25 ` Saqib Khan
2016-09-23 3:33 ` Laszlo Ersek
2016-09-20 19:41 ` Rod Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ed8f5d6-7937-b723-086a-c09afef14d6e@rodsbooks.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox