On Mon, Oct 15, 2012 at 2:18 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Oct 15, 2012 at 11:11:26AM -0700, Greg KH wrote: >> On Mon, Oct 15, 2012 at 01:15:05PM -0400, Mostafa Kassem wrote: >> > Greetings, >> > >> > I am having a problem with usbserial and ftdi_sio kernel loadable modules. >> > >> > I am working on an embedded board using RHEL 6.0. >> >> Wait right there. If you are using RHEL, you need to get support from >> Red Hat for it, especially as you are already paying for it, you should >> use it. Yes, will do. >> > The board has 2 FTDI >> > chips each with quad serial interface for a total of 8 serial ports. >> > In addition, we have a WiFi module that behaves as a USB to Serial >> > converter. >> >> What specific wifi module is this? What driver is it? The FTDI chiprs are of type FT4232 and the Wifi module is this one from connectone: http://www.connectone.com/?page_id=233 >> > I can see in /dev directory that the 8 serial ports from FTDI are >> > mapped as ttyUSB0 to ttyUSB7, however I can't find the WiFi module. If >> > I disable the loading of ftdi_sio.ko module, the WiFi module appears >> > as ttyUSB0 and it works fine. It seems to me that both the WiFi module >> > and the one of the FTDI interfaces want to use ttyUSB0 and it seems >> > that the FTDI interface is winning. >> >> Odd, again, what driver/device is this wifi device? See above, the driver is the generic usbserial. >> >> > Even if I rename the FTDI interfaces from ttyUSB0..7 to fdtisio0..7 , >> > I still don't see the WiFi module. >> > >> > The WiFi module is loaded in rc.local using modprobe usbserial >> > vendor=0x**** product=0x**** as per the WiFi module vendor's >> > recommendations. >> >> Oh, that's the problem, NEVER do that, you just broke things, as you >> found out. No one should ever use the generic usb serial interface, >> newer kernels will warn you about this. Let the proper driver manage >> the wifi device and you will not have any of these issues. I have no choice but to do that, if I don't add the vendor and the product, the WiFi module won't work. Also, the kernel is old (2.6.32), so it does not warn me. The vendor is 0x1af1 and the product is 0x0003. > Also, what is the vendor and product id you are passing to the driver? > That will help us determine what the real driver you should be using > instead. > Also, in another post, you mentioned that usbserial can only deal with one generic device not two, is this the case also here? > thanks, > > greg k-h No, thank you for your help and prompt reply. Mostafa -- 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
