From: vincent guffens <v.guffens@imperial.ac.uk>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: v.guffes@imperial.ac.uk
Subject: Re: Status of UNDI Support
Date: Fri, 10 Mar 2006 09:49:19 +0000 [thread overview]
Message-ID: <44114B9F.5050006@imperial.ac.uk> (raw)
In-Reply-To: <44100C67.6000402@itwm.fraunhofer.de>
I am resending this mail, it looks that it didn't get through:
Martin Vogt wrote:
> Hello grub2 developers,
>
>
> I just tried pxegrub2, but I found out that the network support
> is missing. (can load pxegrub, but no menu.lst or kernel etc....)
>
>
hi,
i have been working on netboot support for grub2 for a while and even
got it working once using code from etherboot.
I am now grubifying the work in order to submit a patch. The PCI support
is on its way and is going to feature an abstract interface which should
ease the merging of new implementations.
> My experience with grub1 and the etherboot based nic support,
> is that it does not work well, so I still use pxelinux.
> I always thought that grub2 wont use etheboot and only supports UNDI,
> like pxelinux.
>
>
>
As far as I know, a lot of problems related to netboot in grub were
linked to the fact that the drivers could not easily be linked together
as it could result in grub freezing of behaving improperly. The idea in
grub2 is still to use the etherboot drivers but not to be limited by
them. There will be a "glue" layer in order to import the etherboot
drivers, hopefully with as little modifications as possible, but it will
be possible to extend that.
> Isnt it possible to re-use some UNDI support from pxelinux and put it
> into grub2?
>
>
>
I don't know very much about this UNDI support but this is certainly not
incompatible with using the etherboot drivers for supported cards
anyway. Grub is very flexible and we can certainly have both support if
it is worth it.
> regards,
>
> Martin
>
>
>
>
--
Vincent Guffens
Intelligent Systems & Networks Group
Research associate, Imperial College
next prev parent reply other threads:[~2006-03-10 9:50 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 [this message]
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
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=44114B9F.5050006@imperial.ac.uk \
--to=v.guffens@imperial.ac.uk \
--cc=grub-devel@gnu.org \
--cc=v.guffes@imperial.ac.uk \
/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.