On Fri, Apr 18, 2014 at 03:37:53PM -0700, Larry Baker wrote: > Greg, > > Any suggestions how to trace what is going on? Going on with what? Was there a bug report in that wall of text that I missed? :) > I see all the tracing debug code has been removed in the latest > ftdi_sio driver. That's because the kernel provides tracing functionality built-in, no need for it to be on a driver-by-driver basis. Use it if you think it is necessary. > I think it will be easier to first try upgrading the kernel/drivers on > the AtomPC, even though I want to run on an ARM SoC. The ARM SoC I'm > currently using requires some ARM ERRATA in the kernel; exactly which > ones still seems to be a moving target. As you say, the drivers > should be architecture neutral. If a fix for this problem can be > found using an AtomPC, I am confident it will also apply to an ARM > SoC. > > The drivers I'm looking at are all in the usb/serial branch of the > Linux kernel. You recommend discussing this on the > linux-usb@xxxxxxxxxxxxxxx mailing list instead of this one? CC this > one? > > What about my question of vendor supported vs. reverse engineered USB > serial drivers. If there is a chip with (better) vendor Linux driver > support, I can complain to them and they can fix it instead of us. If > you were to buy a USB-to-Serial adapter, which chip would you buy? I would buy an io_edgeport device, but they are really expensive, and no longer in production from what I can tell. Everything else are very cheap devices, with questionable UART silicon. In the end, it all depends on what you want to use the device for, some are much better than others. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
