[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FW: Subsystem Vendor ID assignment
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: FW: Subsystem Vendor ID assignment
- From: Keith Jasinski <jasinski@mortara.com>
- Date: Thu, 25 Feb 1999 13:55:15 -0600
- Delivered-To: pcisig@teleport.COM
- Resent-Date: Thu, 25 Feb 1999 12:26:49 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"kZ9cJ3.0.Rw2.6kQrs"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
To further elaborate (or exacerbate) the question:
The recent release of V2.2 of the spec requires the implementation of
Subsystem Vendor and Device IDs. Why? Is the sole purpose to allow
multiple uses of the same core (PLX, AMCC, Motorola, Intel, whoever)
without replacing their Device and Vendor IDs?
Since the SIG does not assign Subsystem Vendor IDs, just Vendor IDs,
does anyone who has a Vendor ID also have a Subsystem ID (ie: the same
number)?
When Windows does a device recognition, does it have to match all 4 IDs
(both vendor and both device) to recognize a device?
In our case, we are either creating our own core or replaceing the
device and vendor ID with our own. Since V2.2 requires subsystem vendor
and device IDs, do I just replicate the vendor and device IDs in the
subsystem section?
Thanks in advance,
Keith
Keith F. Jasinski, Jr.
jasinski@mortara.com
Extension 245
Mortara Instrument, Inc. (www.mortara.com)
7865 North 86th Street
Milwaukee, WI 53224
(414) 354-1600