RE: Subsystem Vendor and Device IDs

[<ingvar_berg@x400.icl.co.uk>]

It makes a big difference if the controller lives on the mb, because 
that defines the implementation to the OS, by combining the mb ID and 
the controller ID. One possible way to get a "full" ID would be that 
the enumerator SW uses the mb ID as subvendor ID if the subvendor ID 
field is empty in HW.

As for the early, buggy BIOSes: we're discussing how systems delivered 
after January 1, 1997 has to be implemented. Of course one must require 
that they have a BIOS that behaves well...

/Ingvar
----------
From: mek(a)sco.com

From: ingvar_berg@x400.icl.co.uk

most OSes prefer to bypass BIOS and access the HW directly.

Speaking of devices on the motherboard, how comes that Win95 can't
understand that devices in "slot 0" are on the mb, and don't need the
Subsystem IDs?

Huh? Why would where the device lives make any difference as far as whether
something 'needs' a Subsystem ID? That's an O/S requirement not anything
to do with hardware...

As far as slot 0 goes, the only reliable way to get slot in PCI2.1 is via
the
buggy IRQ ROUTING BIOS call. Perhaps Win '95 isn't doing this? Many
BIOSen have this call implemented incorrectly.
Matt


£@
-