The problem is that the information in the device list may
be out of date if setpnp has been used.
Perhaps it will be said that setpnp is a "debugging tool" and
ordinarily one shouldn't change resource assignments, but
setpnp is useful for more than debugging. E.g., with current
kernels it is necessary for me to run setpnp during the boot
sequence in order to set up certain devices properly.
Sometimes, also, there aren't enough IRQs to go around, and
one may use setpnp to disable and enable different devices.
Thus I think that the PnP BIOS driver needs to be fixed so
that it will use and report the correct (current) resource
values. Looking at the code, I see no reason why there
needs to be a device list at all. Functions such as
pnpbios_find_device() could just as well scan through
device info returned (fresh) by the PnP BIOS. I don't
think speed is a big issue here. Are there other reasons
for maintaining a device list in the driver?
-- Thomas Hood jdthood_AT_yahoo.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/