[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Unidentified subject!
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: RE: Unidentified subject!
- From: Dave New <NewD@esi.com>
- Date: Thu, 25 Feb 1999 06:44:49 -0800
- Delivered-To: pcisig@teleport.COM
- Resent-Date: Thu, 25 Feb 1999 07:30:20 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"A2eXy3.0.v91.JGMrs"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
That's one way of doing it. Another way would be to contact the
ATU & Bridge chip vendor and have them assign you a Subsystem ID,
to differentiate your realization behind their bridge from other
vendors. If the ATU & Bridge chip vendor won't/don't support
Subsystem ID's or registration thereof, you might rethink your
decision to use that chipset. Microsoft, in particular, has
made a rather strong statement that they wish to only fully
support PCI agents that implement the Subsystem ID. The idea
is to take the guesswork out of Plug 'n Play device driver
installation.
Cheers,
-- DaveN
> -----Original Message-----
> From: Joe Derham [SMTP:joed@adelphia.net]
> Sent: Monday, February 22, 1999 1:44 AM
> To: Mailing List Recipients
> Subject: Unidentified subject!
>
> Hi Everbody,
>
> The company I work for is building our own card which sits on the
> PCI bus. It has a commercialy available processor on it which has a PCI
> interface (ATU & Bridge). This processor already has it's own
> vendor/device ID associated with it. My question is "How would/should I
> distinquish the processor on my board vs. the same processor on another
> company's board using the same processor?" Do we need to get our own
> Vendor ID assigned to us from PCISIG and set that ID in the processor's
> ROM code?
>
> Thanks In Advance,
> Joe Derham