linux-kernel - Re: Regarding USB-to-Serial device driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Sep 2010 09:56:23 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Raju Rameshwar Uprade <rajsingh@...a.tifr.res.in>
cc:	Greg KH <gregkh@...e.de>, <linux-kernel@...r.kernel.org>,
	<linux-usb@...r.kernel.org>
Subject: Re: Regarding USB-to-Serial device driver

On Mon, 13 Sep 2010, Raju Rameshwar Uprade wrote:

>  Ya I tried with debug=1 on the modprobe line.
> 
> > > f6e80c00 4108452201 C Bo:7:003:2 0 1 >
> > > f6e80900 4108453203 C Ii:7:003:1 0:1 10 = a1200000 00000200 0000
> 
>  same status bytes I am also getting.
>  One thing I would like to ask why it is coming on Ii (Isochronous endpoint)?

"Ii" is Interrupt-IN, not Isochronous-IN.  usbmon uses 'Z' for 
isochronous.

> output of usbmon tell that data going out properly, but it's going in chunks,Ideally It
> should go out in one chunk.I think I have to take care of RTS line. UART drivers works
> in that way,RTS is enabled for complete data out ,then it is disabled so that we can get
> device response.

Maybe your program writing the data in chunks.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/