Dennis wrote:
I don't think thats the point. The fact is AFAIK know school teaches
hardware detection, except the school of hard knocks, and cheap
chinese knock off components. The fact is if you've ever tried to get
obscure unsupported hardware going, you probably have experience with
hardware detection.
And when it comes down to it, lspci is usually all you need to know ;)
I was thinking more along the lines of doing that programatically. ie:
device drivers/hot plug/cold plug/ etc. (Been staring at the command
line to long today :)
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
I've been considering looking into creation of something similar to
NDISwrapper, for all types of hardware, and then having a bootscript run
lspci against known hardware. If the driver is not present, then just
go wget it unzip/whatever and poof instant hardware driver. Just
recycling the old windows drivers.
Of course this is a pipe dream, that would require quite alot of ifs, to
be in place before it could work.
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
