> Depends. If the drivers allocation is coherent with the vendors description
> in the PnP configuration data, it's a newbus error (it shouldn't try to
> allocate the card there in the first place). If the PnP info differs from
> the drivers view of the card, it's either the vendors fault for providing wrong
> infos (this wouldn't be the only card suffering) [fix: provide a quirk entry],
> or the drivers fault: it should obey what the vendor tells PnP about the
> card. Which case applies? Simple: if it's possible to change the driver to
> obey the cards infos, that should be done. If the driver couldn't be made
> to work support for that card should be removed :-)
Well,
current PnP code has own problems with parsing card data:
* wrong calculation of memory range size (PR: kern/16712 with path).
This bug will hit any card with io memory (ed driver for example).
* inability to parse a little bit complicated config like in
'IBM Auto 16/4 Token-Ring ISA Adapter' -- I am still fighting
with this bug.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
