On Wed, Oct 10, 2012 at 03:05:09PM +0200, Jarkko Huijts wrote: > On Tue, 2012-10-09 at 07:59 -0700, Greg KH wrote: > > On Tue, Oct 09, 2012 at 12:21:56PM +0200, Jarkko Huijts wrote: > > > I have e-mailed FTDI's support to ask whether the assumptions described > > > above are true and whether there is no register to read the actual > > > amount of data in the hardware buffer(s). Their website states you need > > > to sign an NDA to get the register descriptions, but with some luck that > > > isn't needed. > > OK, no luck. I got a reply that pretty much said "please sign this NDA" > and since I'm not a lawyer, I'm not sure whether the conditions would > allow me to use their datasheet for GPL code. > > > Your function looks good, care to add it to the file and create a patch > > so that I can apply it properly to the kernel tree? > > Sure. I've made a patch for the latest stable (v3.6.1) using git. Let me > know if anything if not OK. > > Note: The code shown in this thread was for v2.6.38. Two new types of > FTDI device are supported in v3.6.1. I've updated my code in the same as > ftdi_tiocmget(). The patch looks great, thanks so much for doing this. I'll queue it up after 3.7-rc1 is released by Linus (which should be in a few days). greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html