On Sat, 4 Sep 1999, John-Mark Gurney wrote:
> 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...
We already have a dummy driver (unknown) which can be adapted for this
purpose. Perhaps this is the best solution.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
