linux-kernel - Re: Univeral Protocol Driver (using UNDI) in Linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <44D7579D.1040303@zytor.com>
Date:	Mon, 07 Aug 2006 08:09:17 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Daniel Rodrick <daniel.rodrick@...il.com>
CC:	Linux Newbie <linux-newbie@...r.kernel.org>,
	kernelnewbies <kernelnewbies@...linux.org>,
	linux-net@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Univeral Protocol Driver (using UNDI) in Linux

Daniel Rodrick wrote:
> Hi list,
> 
> I was curious as to why a Universal driver (using UNDI API) for Linux
> does not exist (or does it)?
> 
> I want to try and write a such a driver that could (in principle)
> handle all the NICs that are PXE compatible.
> 
> Has this been tried? What are the technical problems that might come in 
> my way?
> 

It has been tried; in fact Intel did implement this in their "Linux PXE 
SDK".  The UNDI API is absolutely atrocious, however, being based on 
NDIS2 which is widely considered the worst of all the many network 
stacks for DOS.

Additionally, many UNDI stacks don't work correctly when called from 
protected mode, since the interface doesn't work right.  Additionally, 
UNDI is *ONLY* available after booting from the NIC.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/