From: "Raju Rameshwar Uprade" <rajsingh@ncra.tifr.res.in>
To: Greg KH <gregkh@suse.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regarding USB-serial device driver
Date: Wed, 8 Sep 2010 09:11:19 +0530 [thread overview]
Message-ID: <20100908034006.M11954@admin-gateway.ncra.tifr.res.in> (raw)
In-Reply-To: <20100907114913.M69542@admin-gateway.ncra.tifr.res.in>
> Wierd. If you enable debugging in the driver:
> modprobe pl2303 debug=1
> do you also see the kernel log showing extra data going out to the host?
>
> What is your userspace program doing? Are you sure you are only writing
> 6 bytes? The bulk out should only be writing the actual data in the
> buffer, not any more than that.
>
> Do you have an example userspace code that we can use to test with?
>
> thanks,
>
> greg k-h
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
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
f6e80c00 4108452201 C Bo:7:003:2 0 1 >
f6e80900 4108453203 C Ii:7:003:1 0:1 10 = a1200000 00000200 0000
f6e80900 4108453221 S Ii:7:003:1 -115:1 10 <
ee9e1680 4108456262 S Co:7:003:0 s 21 22 0000 0000 0000 0
ee9e1680 4108457202 C Co:7:003:0 0 0
ee9e1680 4108457225 S Co:7:003:0 s 21 22 0003 0000 0000 0
ee9e1680 4108458201 C Co:7:003:0 0 0
f6e80c00 4108458228 S Bo:7:003:2 -115 1 = 40 // don't know from where it is going out
f6e80c00 4108459201 C Bo:7:003:2 0 1 >
ee9e1680 4108463235 S Co:7:003:0 s 21 22 0000 0000 0000 0
ee9e1680 4108464204 C Co:7:003:0 0 0
Regards,
Raj.
next prev parent reply other threads:[~2010-09-08 3:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 6:14 Regarding USB-serial device driver Raju Rameshwar Uprade
2010-09-07 6:59 ` Greg KH
[not found] ` <20100907114913.M69542@admin-gateway.ncra.tifr.res.in>
2010-09-08 3:41 ` Raju Rameshwar Uprade [this message]
2010-09-08 6:17 ` Greg KH
2010-09-08 8:51 ` Raju Rameshwar Uprade
[not found] <20100819055329.M29689@admin-gateway.ncra.tifr.res.in>
[not found] ` <20100819061525.M24093@admin-gateway.ncra.tifr.res.in>
2010-08-19 7:38 ` Regarding USB-Serial Device driver Marek Vasut
2010-08-19 14:18 ` Greg KH
2010-08-20 3:42 ` Raju Rameshwar Uprade
2010-08-20 3:56 ` Greg KH
2010-08-20 6:56 ` Raju Rameshwar Uprade
2010-08-20 15:39 ` Greg KH
[not found] ` <AANLkTin8AiOj4CST5Dr_icnY4MugG1mhgP7=c1jgcJcA@mail.gmail.com>
2010-08-31 4:05 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-08-19 6:28 Raju Rameshwar Uprade
2010-08-19 13:09 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100908034006.M11954@admin-gateway.ncra.tifr.res.in \
--to=rajsingh@ncra.tifr.res.in \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).