[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: what is put in Vendor ID and Device ID?
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: what is put in Vendor ID and Device ID?
- From: "Monish Shah" <monish@poboxes.com>
- Date: Thu, 29 Oct 1998 17:59:58 -0700
- Delivered-To: pcisig@teleport.com
- Resent-Date: Fri, 30 Oct 1998 11:42:22 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"kjJUk3.0.MO1.qCHEs"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
> From: Dave New <NewD@esi.com>
> > From: Mark Galecki [SMTP:marek@greenspring.com]
> > The PCI spec, rev 2.1 implies that Vendor ID and Device ID belong to a
PCI
> > "device" or "controller", which is a component that confirms to
electrical
> > reqs of a local PCI bus. But an empty PGA does not by itself conform
to
> > anything particular. I have to program it to conform. I have to make
the
> > "PCI function". So does empty PGA qualify as a device and therefore
> > should
> > have its ID's present in Vendor and Device ID?
> >
> [Dave New] When you say "empty PGA" I believe you mean
> that it has some basic PCI agent functionality, but
> so far, it can be treated as some kind of generic
> conduit to some addon circuitry...
I don't think he meant that. An empty PGA is a bunch of gates with no
paritcular functionality. So, if you program it to be a PCI device, you
should use your own vendor ID and device ID, not that of the PGA vendor.
In fact, there is no guarantee that the PGA vendor even has a vendor ID.
Even if they do, they manage their own device IDs internally, so you can't
just make on up on their behalf. So, from a practical perspective, there
is no option but to use your own IDs.
Monish Shah
Ascent Software