[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Subsystem IDs and their meaning
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: Subsystem IDs and their meaning
- From: Dan Mick <dan.mick@West.Sun.COM>
- Date: Mon, 5 Jan 1998 16:00:09 -0800 (PST)
- Reply-To: Dan Mick <dan.mick@West.Sun.COM>
- Resent-Date: Mon, 5 Jan 1998 16:14:35 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"B-I5e2.0.dn4.-ENiq"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
Since enough people have privately or publicly mentioned the case
of SSVID/SSID being zero, let me clarify:
I didn't intend to consider the case of 0; 0 is "unimplemented",
and clearly an unimplemented value should never be used to bind
a driver.
So the choice between "is SSVID/SSID itself enough" (choice 1)
and "SSVID/SSID only have meaning in the context of VID/DID" (choice 2)
*assumes* that SSVID/SSID are implemented (i.e. nonzero).
I'm also not asking anything about the wisdom of requiring a nonzero
SSVID/SSID.