Re: CONFIG_PNP: Please change the name
Mike Kilburn (duxmike@iafrica.com)
Sun, 17 Mar 1996 21:28:22 +0200
> Run. I like Jumpers on a card much more, there I can actually see and be
> sure whats going on. The Problem ist not the PNP itself, but the mixture
> with non PNP Components, the Software Requirements and the Bios Extensions.
>
Yes. But I assume these are software issues that can be overcome by
a properly written resource manager for linux. I like jumpers but
the promise of a system where you just "plug and play" is to tempting
to pass up.
> A good Example are the new Teles 1.3 ISDN Cards. You can configure them
> only under Windows or dos, and you can only stick two of them in one system
> cause they have only 2 config-ports.
>
But thats a fault of Teles. Non PnP soft config works well with the 3com
enet cards. Again, a good resource manager should do the best it can
with the hardware at hand.
> Of course PNP is very helpfull (Eisa, MCA, PCI) if it works right... the
> question is... does it work right? :)
>
This is the big question. I am only concerned with linux for now so if
PnP for linux works well I dont care if Win95 is a "disaster".
We have the option to disable PnP with a jumper and then we have a
"simi" soft config. The config port is jumpered in that case but the dual
port ram and irq is soft config via the jumpered i/o.
Regards,
Mike Kilburn