On Tue, Mar 22, 2011 at 11:07:46PM -0700, Guenter Roeck wrote: > On Wed, Mar 23, 2011 at 01:41:53AM -0400, Bernhard Walle wrote: > > * Greg KH <greg@xxxxxxxxx> [2011-03-23 05:50]: > > > > > > It should, you can talk to the device from userspace using that virtual > > > serial port, right? Isn't that what you need to do here? > > > > > > Why try to create a new type of interface to the device from what it was > > > supposed to be by the manufacturer? > > > > The device is multi-function. It's quite common to use some (extended) > > USB-to-serial-converters also for serial busses like I²C or SPI. I know > > that from the FT2232C chip. > > > > Using such a device as normal Linux I²C device makes perfectly sense, > > IMO. > > > Correct. I use and need it as I2C bus controller. FWIW, that is what it is sold > for. User space access doesn't help me there. > > Anyway, the only reason for submitting the driver was that I thought it might > be useful for others. Maybe not useful enough, and defintely not worth arguing > about it. I'll make it available as stand-alone driver; that should be good enough. No need for that, we want drivers in the kernel tree. But, if this just duplicates the cdc-acm interface, and it looks like it does, I don't think you need a kernel driver at all for it. Just use userspace commands to the serial port, like you do on Windows, and all should be fine, right? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
