From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: UNDI/PXE for 2.4.x available?
Date: 4 Feb 2002 08:31:01 -0800 [thread overview]
Message-ID: <a3md05$ps3$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020204154633.E2BC267F3@penelope.materna.de>
Followup to: <20020204154633.E2BC267F3@penelope.materna.de>
By author: Tobias Wollgam <tobias.wollgam@materna.de>
In newsgroup: linux.dev.kernel
>
> Hello,
>
> is there a UNDI (Universal Network Driver Interface, a part of the
> PXE-specification) for the 2.4x kernel available?
>
> We found one from Intel in its linux-pxe-sdk for the 2.2.x kernel. This
> one works, but not with all pxe-networkcards.
>
I think you'll have that problem with any UNDI driver; in either case
I suspect that (a) performance will stink no matter what and (b) it
won't work properly with SMP unless you apply really heavy locking.
The PXE people at Intel really seems enamored with the idea of using
the UNDI stack all the way into the operating system; I don't think
any sane operating system does that (DOS, of course, does, but DOS
isn't a sane operating system.) If I'm not completely mistaken UNDI
was derived from NDIS 2 or so -- widely considered the crappiest of
all the various specifications for DOS drivers.
> Potentially we will port it from 2.2 to 2.4 or rewrite it for 2.4 with
> a little assistance.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-02-04 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 15:46 UNDI/PXE for 2.4.x available? Tobias Wollgam
2002-02-04 16:31 ` H. Peter Anvin [this message]
2002-02-04 17:08 ` Tobias Wollgam
2002-02-04 17:32 ` H. Peter Anvin
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='a3md05$ps3$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox