From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Status of UNDI Support
Date: Fri, 10 Mar 2006 22:55:26 +0100 [thread overview]
Message-ID: <87slpqt169.fsf@xs4all.nl> (raw)
In-Reply-To: <20060310154510.GA11141@soul.cs.tau.ac.il> (Yedidyah Bar-David's message of "Fri, 10 Mar 2006 17:45:10 +0200")
didi@tau.ac.il (Yedidyah Bar-David) writes:
> On Fri, Mar 10, 2006 at 03:07:36PM +0100, Marco Gerards wrote:
>> Martin Vogt <vogt@itwm.fraunhofer.de> writes:
>> > Isnt it possible to re-use some UNDI support from pxelinux and put it
>> > into grub2?
>
> While I do not know the internals of grub2, I guess some parts of it run
> in protected mode, while pxelinux is realmode only. I think this means
> it won't be easy to use parts of it.
GRUB is able to switch to realmode and back. It's what's done when
accessing the BIOS to read from disk.
>>
>> I don't know. I think it is better that we write it ourselves, it
>> does not appear too hard to implement...
>
> Looking at the sources of pxelinux, it seems somewhat more complex than
> what you can tell from reading the specs, mainly because you want, as
> reasonably as possible, to support also buggy PXE stacks etc. So while
> it's probably not that hard, it would make sense to look at pxelinux for
> reference if not for the code.
>
> I personally was a user of both etherboot, grub with etherboot drivers
> and grub with undi (which indeed did not work well for me back then - I
> did not try it recently), and I agree it would make more sense for grub2
> to support undi only, unlike grub legacy which tried to support
> everything etherboot supported, which was probably too much
> synchronization work and therefore did not work well.
I prefer to support both. The etherboot drivers usually work better
than UNDI, AFAIK. But when etherboot does not support a card, people
can fall back to UNDI. Don't forget that not all cards support UNDI,
so I don't want UNDI only.
--
Marco
next prev parent reply other threads:[~2006-03-10 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 11:07 Status of UNDI Support Martin Vogt
2006-03-09 11:36 ` vincent guffens
2006-03-10 9:49 ` vincent guffens
2006-03-10 14:07 ` Marco Gerards
2006-03-10 14:39 ` Martin Vogt
2006-03-10 21:48 ` Marco Gerards
2006-03-10 15:45 ` Yedidyah Bar-David
2006-03-10 21:55 ` Marco Gerards [this message]
2006-03-11 9:04 ` Vesa Jääskeläinen
2006-03-11 14:42 ` Marco Gerards
2006-03-12 22:25 ` Yoshinori K. Okuji
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-all 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=87slpqt169.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.