On Nov 21, 2011, at 10:47, Rolf Eike Beer wrote: >> The pci ID we use is not registered, and except for this driver, which >> is a non-driver really (UIO), the FPGA firmware and the userspace code is >> proprietary. > > Why keep people doing this? This is just asking for future trouble. And it > gives bad karma. This is a bit off topic... Still, to address it: ... because when developing a complex product with limited staff, you prioritize. Unless I am mistaken, my use of PCI ids is to match our HW device with our driver (which is yet not meant to be merged to mainline) in our completely controlled system (hw, kernel, software) made into a product. So we didn't feel it necessary to assign guaranteed unique IDs. If there are any ID conflicts one day, I assume it would be because of a new kernel version we put in, or a new hardware device we put in and in any case, a new release of the product which is thoroughly tested before released. Furthermore, in the unlikely event we do encounter a collision, we can change both the FPGA and the driver on a dime. Am I missing something? What kind of future trouble are you referring to? > > Go and ask your FPGA vendor to assign a device id to you. At least for > Xilinx this has worked. Thanks for the tip, we could look into this if we need to. > > Eike -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
