I don't believe that Win2k does it (it's not from the PnP family, is it?).
But, I don't doubt that XP does it on contemporary hardware. It requires
ACPI support in the BIOS. And, ACPI enumerates all of the legacy devices
in the system.
So, we're still relying on the firmware to tell us what's there. One of
the points of this thread, and many others, is that you can't rely on it.
Every BIOS is buggy.
Personally, I like the idea of dumping the firmware tables (DMI, ACPI,
etc) during early init, then letting a userspace program telling the
kernel what is there based on what the firmware says. If we know a
particular table in a particular BIOS is bad, we can ignore it or work
around it.
The auto-config tool can use either what the kernel knows (as exported to
userland), or it can use some parsing tool to parse the tables (with the
same intelligence to know which tables are borked).
And, don't forget that most Windows OSes punt on some hardware. That's why
there's the nice "Add New Hardware" wizard...
-pat
-
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/