linux-kernel - Re: Regarding USB-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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100908061719.GA23233@suse.de>
Date:	Tue, 7 Sep 2010 23:17:19 -0700
From:	Greg KH <gregkh@...e.de>
To:	Raju Rameshwar Uprade <rajsingh@...a.tifr.res.in>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Regarding USB-serial device driver

On Wed, Sep 08, 2010 at 09:11:19AM +0530, Raju Rameshwar Uprade wrote:
> Greg, 
>       I am really sorry, that superfluous data was due to user space program.I have
> modified that.Now I am able to send correct data to the device. 5e and 40 is also going
> out.I don't know from where it is coming.
> But I am not getting the response.
> 
> output of usbmon :
> 
> ee9e1680 4108443204 C Co:7:003:0 0 0
> f6e80c00 4108443237 S Bo:7:003:2 -115 9 = 05080000 00000000 f8 // correct data bytes 

Good.

> f6e80c00 4108444202 C Bo:7:003:2 0 9 >
> ee9e1680 4108448251 S Co:7:003:0 s 21 22 0000 0000 0000 0
> ee9e1680 4108449202 C Co:7:003:0 0 0
> f6e80700 4108450204 C Bi:7:003:3 0 1 = 00
> ee9e1680 4108450546 S Co:7:003:0 s 21 22 0003 0000 0000 0
> f6e80900 4108451204 C Ii:7:003:1 0:1 10 = a1200000 00000200 0400
> f6e80900 4108451223 S Ii:7:003:1 -115:1 10 <
> ee9e1680 4108451227 C Co:7:003:0 0 0
> f6e80c00 4108451252 S Bo:7:003:2 -115 1 = 5e // don't know from where it is going out 

Something wrote it to the driver, did you try it with "debug=1" on the
modprobe line to see what the driver thinks is happening?

> f6e80c00 4108452201 C Bo:7:003:2 0 1 >
> f6e80900 4108453203 C Ii:7:003:1 0:1 10 = a1200000 00000200 0000

This was some status bytes coming back, are you sure you got the line
settings correct?

Your example .c file showed no line settings being set, so you have no
idea what baud rate you are sending at, or what the flow control is, or
anything else like that.  Please be sure to set that up properly to
verify that you really are getting the data out to the device properly.

thanks,

greg k-h
--
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/