Date: Sat, 4 Sep 1999 11:10:10 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Doug Rabson <dfr@nlsystems.com> Cc: "Zach N. Heilig" <znh@thequest.net>, freebsd-current@FreeBSD.ORG Subject: Re: PNP ids missing in sio.c Message-ID: <19990904111010.41861@hydrogen.fircrest.net> In-Reply-To: <Pine.BSF.4.10.9909041518200.2081-100000@salmon.nlsystems.com>; from Doug Rabson on Sat, Sep 04, 1999 at 03:20:00PM %2B0100 References: <19990904060615.A32986@murkwood.znh.org> <Pine.BSF.4.10.9909041518200.2081-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson scribbled this message on Sep 4: > > This is of course a special case, a cranky network card and a > > non-compiling driver for it. If the new pnp code avoids using resources > > hard-wired to non-pnp isa devices (it may, I changed hardware before the > > code was fixed), there shouldn't be any problems. It was an excellent > > excuse to boot that nic anyway. > > The trick for this is to make sure that the config file contains accurate > descriptions of all your non-pnp hardware. In this case, if you have: > > device ed0 at isa? port 0x300 irq 5 ... > > then the subsequent pnp probes should avoid those port and irq settings. but the problem is that he couldn't have the line in because the driver wouldn't compile... so are we going to add a dummy isa device that takes up resources so that this won't happen again? maybe the user has some win95 only isa card or something... but this needs to be able to be configured... along w/ doing this at boot -c time too... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990904111010.41861>