Re: [irda-users] es620 dongle

[Samuel O. <sa...@so...>]

Hi Rob,

On Thu, Jun 15, 2006 at 04:55:05PM +0200, rob heemskerk wrote:
> I came across the text below, telling about the MA620 dongle, which seems to 
> be quite related to the problem I have with the ES620 USB-IrDA dongle. I 
> don't know whether it holds or not.
> I'm including the USB information from the dongle and hope you can help me 
> out. I've found some clues saying that I should rebuild the PL2303 
> (kernel)module as a separate one, but I'm too unfamiliar with that kind of 
> stuff to do it myself.
> 
> I've tried to solve the problem using specific vendor-id and product-id with 
> usbserial, but that will complain:
> 	kernel: usb 1-2.2: new low speed USB device using ohci_hcd and address 6
> 	kernel: usbserial_generic 1-2.2:1.0: Generic converter detected
> 	kernel: usbserial_generic 1-2.2:1.0: Generic device with no bulk out, not 
> allowed.
> 	kernel: usbserial_generic: probe of 1-2.2:1.0 failed with error -5
> 
> So, I don't have the knowledge to solve the problem, I do have the hardware to 
> test a solution to it.
> Could you have a look?
Well, if the ES620 is similar to the MA620, then you don't need to mess up with
usbserial. You should enable the pl2303 driver as a module from your .config 
file, since it pulls the usbserial code automatically. Then plug your dongle
and check if the pl2303 module gets loaded.
If not, then add the ES620 USB vendor and product IDs to the pl2303.c code and
try again.
If that works now, and if Martin is correct, you will need to insmod the 
ma600-sir module on top of the pl2303 one. Assuming that everything went fine,
you will just need to "irattach irda0 -d ma600 -s", and you're done.

That's quite a lot of ifs, so please let us know how it goes ;-)

Cheers,
Samuel.


> Many thanks in advance,
> Rob.
> 
> 
> 
> Bus 001 Device 006: ID 07d0:4100 Dazzle
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0
>   bDeviceProtocol         0
>   bMaxPacketSize0         8
>   idVendor           0x07d0 Dazzle
>   idProduct          0x4100
>   bcdDevice            0.00
>   iManufacturer           1 Kingsun Semiconductor
>   iProduct                2 USB to Serial
>   iSerial                 0
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           41
>     bNumInterfaces          1
>     bConfigurationValue     1
>     iConfiguration          4 USB to Serial
>     bmAttributes         0x80
>     MaxPower              100mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           2
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass     85
>       bInterfaceProtocol      0
>       iInterface              0
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x81  EP 1 IN
>         bmAttributes            3
>           Transfer Type            Interrupt
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0008  1x 8 bytes
>         bInterval               1
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x02  EP 2 OUT
>         bmAttributes            3
>           Transfer Type            Interrupt
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0008  1x 8 bytes
>         bInterval               1
> 
> 
> 
> 
> 
> 	[Written by Martin Diehl <li...@md...>, modified by me]
> 
> > > > i've bought a irda-usb dongle MA620 and i can't get it work with
> > > > kernel driver irda-usb.c - it's not supported. Does anybody have
> > > > experince with this?
> 
> I don't have this hardware, but a few comments anyway:
> 
> 1) Despite it's an USB device the MA620 has nothing to do with the
> IrDA-USB class spec. Therefore irda-usb.c is not the right driver.
> 
> 2) Reportedly the MA620 is made by glueing a SIR encoder+transceiver to a
> pl2303 usb-to-rs232 bridge. Therefore the required setup is basically
> irtty on top of the usbserial+pl2303 driver - maybe the device id's have
> to be added to the pl2303 driver.
> 
> 3) Furthermore it was also said the SIR silicon appears to be connected to
> the pl2303 the same way which is used for the MA600 serial dongle.
> Therefore the ma600 dongle protocol is needed on top of irtty.
> 
> 4) With 2.4.x any setup with irtty (or similar drivers like ppp) on top of
> usb-serial has severe problems (might sleep with spinlock held). To fix
> this, backporting the usbserial from 2.6 would be required - which is
> rather unlikely to happen AFAICS. Furthermore even with this fixed the old
> irtty from 2.4.x has some potential locking issues wrt. tty and network
> layer. In conclusion irtty over usb will not work with 2.4 - sorry!
> 
> 5) In 2.6 the usbserial issue is fixed and we have the new irtty-sir
> there. I know from my own 2.6-testing pl2303/usbserial/sir_dev/irtty-sir
> are all working together happily with some supported serial dongle behind
> an usb-to-rs232 bridge. Hence the remaining issue is to get the converted
> ma600 dongle driver working. This should be pretty easy if the MA620
> internal wiring is really the same as MA600 and someone with the hardware
> would do the required testing.
> 
> 6) You need to use irattach version 0.9.16-pre7 or later
> 
> 
> 
> _______________________________________________
> irda-users mailing list
> ird...@li...
> http://lists.sourceforge.net/lists/listinfo/irda-users