Date: Tue, 5 Dec 1995 13:46:02 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: hasty@rah.star-gate.com (Amancio Hasty Jr.) Cc: hackers@freebsd.org Subject: Re: plug n play detection and initialization Message-ID: <199512052046.NAA00238@phaeton.artisoft.com> In-Reply-To: <199512051859.KAA00341@rah.star-gate.com> from "Amancio Hasty Jr." at Dec 5, 95 10:59:23 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > How does one detect and initialize a Plug N Play ISA card? There is a nice book on this out. There is also a 200 page PostScript document from ftp.microsoft.com. If you are a Microsoft Level 2 developer or better, in the DDK\Docs directory, there is an MS Word file Pnp.doc and a help file Pnp.hlp. Basically, it helps if you know the card is there. The win is on avoiding jumper settings, not on avoiding card specific drivers. Windows 95 handles pnp autodetection by going through a destructive probe sequence and relying on the user to reboot "if it takes too long", and then the sequence can be restarted, skipping whatever hung. This happens both on the initial install and on "add new hardware". For PCI and MCA, you can just ask the bus for card/vendor ID's. For EISA, you can do the same, if you know the memory aperture, which is not required to be the typical 1K by the EISA spec, and so a truly compliant EISA PNP requires the ability to make EISA BIOS calls. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512052046.NAA00238>