linux-kernel - Re: extra large DMA buffer for PCI-E device under UIO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <A8A9A42D-B960-4188-9C81-83FB25E1106D@gmail.com>
Date:	Mon, 21 Nov 2011 11:01:01 -0500
From:	Jean-Francois Dagenais <jeff.dagenais@...il.com>
To:	Rolf Eike Beer <eike-kernel@...tec.de>
Cc:	"Hans J. Koch" <hjk@...sjkoch.de>, Greg KH <gregkh@...e.de>,
	tglx@...utronix.de, linux-pci@...r.kernel.org,
	open list <linux-kernel@...r.kernel.org>,
	Simon Goyette <goyettes@...atest.com>
Subject: Re: extra large DMA buffer for PCI-E device under UIO

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/