Re: unregistered PCI vendor and device IDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thierry Reding wrote:
> * Greg KH wrote:
> > On Fri, Oct 02, 2009 at 04:51:21PM +0200, Thierry Reding wrote:
> > > Hi,
> > >
> > > I'm currently working on a platform that comes with an FPGA connected
> > > to the CPU via a PCIe interface The FPGA will eventually integrate
> > > several IP cores, some of them being open (OpenCores). I would like to
> > > mainline any drivers for those cores, but that raises the problem of
> > > the vendor ID. Is there any procedure for providing Linux drivers
> > > supporting devices which do not have a registered vendor and/or device
> > > ID?
> >
> > Why do you not have a registered vendor device id?  You aren't "allowed"
> > to create a PCI device without one from what I can tell.
> 
> Because my employer has never had a need for one before. The devices will
>  be embedded and from what I hear it seems common practice to just assign
>  vendor and device IDs at random in embedded devices. The reason being that
>  the hardware is always known and there won't be any ID clashes.
> 
> In this particular case it would also not be correct to specify our vendor
>  ID (assuming we actually had one) since some of the IP cores were not
>  developed in-house and are in fact open.

You could ask your FPGA vendor if they will give you one of their device ids. 
Our company got our first device ids for our PCIe boards that way before we 
applied for our own id at PCI SIG.

Greetings,

Eike

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux