[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: Steve Kappes <steve@iphase.com>
- Date: Mon, 05 Jan 1998 17:48:12 -0600
- Cc: pci-sig@znyx.com
- Organization: Interphase Corporation
- References: <199801051943.LAA01631@utopia.West.Sun.COM>
- Resent-Date: Mon, 5 Jan 1998 16:01:46 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"81zJi1.0.jX4.P6Niq"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
- Sender: steve@iphase.com
Number two is the most correct. If only one field was required,
there would be only one field. Personally I don't see any
reason to have required the subsystem field. A unique vendor and
device ID with a zero subsystem ID should have been enough
to indentify a device.
Dan Mick wrote:
>
> Hi, all. There seems to be a difference of opinion about the
> interpretation of the spec WRT Subsystem IDs. I've asked Warren
> Questo at Intel to help clarify, but have gotten no response as yet.
>
> Can I run a quick opinion poll?
>
> How many of you think either of the below? (I believe them to be
> mutually-exclusive, so you can't think both.):
>
> 1) The Subsystem Vendor ID and Subsystem ID can be used, by
> themselves, as the only pieces of information to uniquely identify a
> given PCI device (i.e. 32 bits of config space is a
> unique-in-all-the-world identifier for "this device in this
> subsystem").
>
> 2) The Subsystem Vendor ID and Subsystem ID can be used only in
> conjunction with the Vendor ID and Device ID to uniquely identify a
> given PCI device. (i.e. 64 bits of config space is a
> unique-in-all-the-world identifier for "this device in this
> subsystem".)
>
> Raise your e-hands, please, 1 or 2 (privately or publicly, as you
> like, and I'll summarize, anonymously or otherwise, as you like).
>
> ---
>
--
Steve Kappes Interphase Corp. steve@iphase.com