[plug] Dolphin USB -> Serial adaptor

[Ryan]

Hi PLUG,

I'm trying to get a Dolphin USB -> Serial adaptor working in Linux.  If
I can't I'll just take it back and get a Belkin one which I know has
support, but that's further to drive :)  I've tried the bf2.4.18 and
2.4.21-pre4 kernels with Debian.

/proc/bus/usb/devices says this about it:

C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0b39 ProdID=0421 Rev= 2.00
S:  Manufacturer=OCT Inc.
S:  Product=OCT USB to SERIAL
S:  SerialNumber=OCAQ241T

Some hits on google suggest the OCT products use the FTDI module, I
tried that and it does nothing, so back to generic serial.

I can do: insmod usbserial vendor=0xb39 product=0x421 and it will say:

Mar 21 13:04:09 vaio kernel: usb.c: registered new driver serial
Mar 21 13:04:09 vaio kernel: usbserial.c: USB Serial support registered
for Generic
Mar 21 13:04:09 vaio kernel: usbserial.c: Generic converter detected
Mar 21 13:04:09 vaio kernel: usbserial.c: Generic converter now attached
to ttyUSB0 (or usb/tts/0 for devfs)
Mar 21 13:04:09 vaio kernel: usbserial.c: USB Serial Driver core v1.4

Goodo.  Then I crank up minicom or cat and talk to a router on
/dev/ttyUSB0 I get a constant:

1'1'1'1'1'1'1'1'1'1'1'1'1'1'1'1'1'1' output by the device whenever
something tries to talk to anything attached to it.  Debug on the
modules just produces pages and pages of logging of the 1' output
without saying anything evidently errorsome.

Mar 21 13:04:57 vaio kernel: usbserial.c: generic_read_bulk_callback -
port 0
Mar 21 13:04:57 vaio kernel: usbserial.c: generic_read_bulk_callback -
length = 2, data = 31 60

And yes:
0x31 = ASCII 49 = 1
0x60 = ASCII 96 = '

When on a standard serial port minicom behaves, so I know what I'm doing
to some degree :)

The LED on the adaptor blinks away like you'd expect and everything else
appears normal.

Does anyone have a suggestion?  Is this probably just some nutty chipset
not yet supported fully and I should go and try the Belkin one, or is
there something obvious that hit any of you that you care to share?

Thanks,

Ryan