From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Rodrick <daniel.rodrick@gmail.com>
Cc: 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: Tue, 08 Aug 2006 09:35:29 -0700 [thread overview]
Message-ID: <44D8BD51.8040206@zytor.com> (raw)
In-Reply-To: <292693080608072213n2be75176g46199e92d669f5de@mail.gmail.com>
Daniel Rodrick wrote:
>
> Hi ... so there seem to be no technical feasibily issues, just
> reliabliy / ugly design issues? So one can still go ahead and write a
> Universal Protocol Driver that can work with all (PXE compatible)
> NICs?
>
For some definition of "all" = meaning "it might work on some of them."
> Are there any issues related to real mode / protected mode?
Yes, a whole bunch of PXE/UNDI stacks are broken in protected mode.
-hpa
next prev parent reply other threads:[~2006-08-08 16:35 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 [this message]
2006-08-07 18:00 ` Jan Engelhardt
2006-08-07 18:00 ` Jan Engelhardt
2006-08-07 18:15 ` H. Peter Anvin
-- 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=44D8BD51.8040206@zytor.com \
--to=hpa@zytor.com \
--cc=daniel.rodrick@gmail.com \
--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.