Re: Attaching MEGAWIN USB Bridge with USB generic driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 26 Nov 2009, Marian wrote:

> Hi all!
> 
> I have to attach the MEGAWIN USB Bridge (vid=0x0e6a, pid=0x0101) to my Linux 
> kernel. I followed the instructions in the kernel documentation and don´t know 
> if either the driver finally doesn´t fit for the device or I have forgotten to 
> configure something.

What is this device?  What is it supposed to do?

> Please have a look at the output:
> 
> dmesg after calling "insmod usbserial vendor=0x0e6a product=0x0101" and plug-
> in of the device:
> 
> [...]
> usbcore: registered new driver usbserial
> drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
> usbcore: registered new driver usbserial_generic
> drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
> hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0004
> brcm-ehci brcm-ehci.0: GetStatus port 2 status 001403 POWER sig=k  CSC CONNECT
> hub 1-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
> hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501
> brcm-ehci brcm-ehci.0: port 2 low speed --> companion
> brcm-ehci brcm-ehci.0: GetStatus port 2 status 003002 POWER OWNER sig=se0  CSC
> hub 1-0:1.0: port_wait_reset: err = -134
> hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0004
> brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [1] = 0x00010301 CSC 
> LSDA PPS CCS
> hub 2-0:1.0: port 2, status 0301, change 0001, 1.5 Mb/s
> hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x301
> brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [1] = 0x00100303 PRSC 
> LSDA PPS PES CCS
> usb 2-2: new low speed USB device using brcm-ohci-0 and address 3
> brcm-ohci-0 brcm-ohci-0.0: GetStatus roothub.portstatus [1] = 0x00100303 PRSC 
> LSDA PPS PES CCS
> usb 2-2: default language 0x0409
> usb 2-2: new device strings: Mfr=0, Product=2, SerialNumber=0
> usb 2-2: Product: USB Bridge
> usb 2-2: hotplug
> usb 2-2: adding 2-2:1.0 (config #1, interface 0)
> usb 2-2:1.0: hotplug
> usbserial_generic 2-2:1.0: usb_probe_interface
> usbserial_generic 2-2:1.0: usb_probe_interface - got id
> usbserial_generic 2-2:1.0: Generic converter detected
> usbserial_generic 2-2:1.0: Generic device with no bulk out, not allowed.
> usbserial_generic: probe of 2-2:1.0 failed with error -5
> hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0004

This error message indicates that the device cannot be used as a serial
interface, since it doesn't have any bulk endpoints.  So usbserial
isn't the right driver for it.  Also, it runs at low speed (1.5 Mb/s) 
and doesn't have any way to send data to the computer -- the listing 
below shows that it is output only.

> root@dm800:~# cat /proc/bus/usb/devices

> T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=1.5 MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0e6a ProdID=0101 Rev= 5.10
> S:  Product=USB Bridge
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=03(O) Atr=03(Int.) MxPS=   8 Ivl=10ms

This doesn't tell much about what the device is intended for.  It uses 
a vendor-specific communications protocol, so Linux might not have any 
drivers for it.

Alan Stern

--
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

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux