From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Daniel Rodrick <daniel.rodrick@gmail.com>,
Linux Newbie <linux-newbie@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Univeral Protocol Driver (using UNDI) in Linux
Date: Mon, 07 Aug 2006 11:15:19 -0700 [thread overview]
Message-ID: <44D78337.40109@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0608071958160.3365@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>> Agreed. But still having a single driver for all the NICs would be
>> simply GREAT for my setup, in which all the PCs will be booted using
>> PXE only. So apart from performance / relilability issues, what are
>> the technical roadblocks in this?
>
> Netboot, in the current world, could be done like this:
>
> 1. Grab the PXE ROM code chip manufacturers offer in case your network card
> does not support booting via PXE yet and write it to an EPROM which most
> PCI network cards have a socket for
>
> 2. Use PXELINUX, boot that with the help of the PXE ROM code
>
> 3. Put all drivers needed into the kernel or initrd; or send out different
> initrds depending on the DHCP info the PXE client sent.
>
There is a program called "ethersel" included with PXELINUX which can be
used to send out different initrds depending on an enumeration of PCI space.
-hpa
next prev parent reply other threads:[~2006-08-07 18:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 10:39 Univeral Protocol Driver (using UNDI) in Linux Daniel Rodrick
2006-08-07 15:09 ` H. Peter Anvin
2006-08-07 16:11 ` Daniel Rodrick
2006-08-07 16:49 ` H. Peter Anvin
2006-08-08 5:13 ` Daniel Rodrick
2006-08-08 5:13 ` Daniel Rodrick
2006-08-08 15:04 ` Alan Shieh
2006-08-10 8:18 ` Daniel Rodrick
2006-08-10 8:18 ` Daniel Rodrick
2006-08-11 20:01 ` Alan Shieh
2006-08-10 20:59 ` Donald Becker
2006-08-10 20:59 ` Donald Becker
2006-08-10 21:08 ` H. Peter Anvin
2006-08-11 20:48 ` Alan Shieh
2006-08-11 20:48 ` Alan Shieh
2006-08-08 16:35 ` H. Peter Anvin
2006-08-07 18:00 ` Jan Engelhardt
2006-08-07 18:00 ` Jan Engelhardt
2006-08-07 18:15 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-28 9:59 Deepak Gupta
2006-09-28 9:59 ` Deepak Gupta
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=44D78337.40109@zytor.com \
--to=hpa@zytor.com \
--cc=daniel.rodrick@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-newbie@vger.kernel.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.