Greg KH <[EMAIL PROTECTED]> writes:
> On Mon, Jun 05, 2006 at 06:05:12PM +0400, Sergei Organov wrote:
>> Hello,
>> 
>> I'm using usbserial module to talk to a device supporting 2 bulk
>> endpoints (high speed USB 1.1).
>
> Which usb-serial driver are you using?  Or are you just using the
> generic driver?

Yes, I'm using generic driver loaded as following:

# modprobe usbserial vendor=0x0c96 product=0x0047 debug=1

[Hmm... I hoped "usbserial module" was exact description of what I'm using,
but obviously it is not, so why isn't it called "usbgeneric" in the
first place to minimize confusion?]

>
>> The input from the device to the host is OK. However, when I write a
>> sequence containing CR and/or LF to the device, the device sees fake
>> 0x80 just before CR and/or LF, and I see this fake 0x80 in the debug
>> output of usbserial/generic modules as well.
[...]

>> The tty settings are:
>> 
>> osv:~# stty -F /dev/ttyUSB0 -a
>> 
>> speed 9600 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\;
>> erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; start = ^Q;
>> stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O;
>> min = 0; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread clocal
>> -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr
>> -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -opost -olcuc -ocrnl onlcr
>> -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon
>> -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt
>> -echoctl -echoke
>
> If the generic one, none of these line settings are "real", it's just a
> data pipe.  If not, please let us know.

It's the generic one, but I believe some of the settings are real, e.g.,
cread, clocal, min, time, etc., isn't it? I just thought that maybe tty
layer messes something due to its setting, for usbserial, according to
its debug output, has been told to write this fake 0x80 from outside
(from tty layer if I understand things correctly).

In the 2.4.x days I even wrote special usb tty driver for the device as
at that time the generic one had a lot of problems with high-speed
transfers, but now I've hoped the generic one will do and it indeed
seems to work well for incoming data, but those write problem makes me
crazy.

And yes, I've hoped it's something simple and known, but as it seems it
isn't, I'll need to do more debugging on my side. Any hints on how to
debug this further?

-- 
Sergei.


_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to