From: Johan Hovold <johan@kernel.org>
To: Ajay Garg <ajaygargnsit@gmail.com>
Cc: Johan Hovold <johan@kernel.org>, Peter Stuge <peter@stuge.se>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Likely issue with ch341 kernel-module/driver
Date: Thu, 27 Aug 2015 09:37:59 +0200 [thread overview]
Message-ID: <20150827073759.GC32712@localhost> (raw)
In-Reply-To: <CAHP4M8Vm2yH-3+ptKe_21QKSt+WikEFXTcQnAL1zgKm=iCYk8A@mail.gmail.com>
[ Please avoid top-posting. ]
On Thu, Aug 27, 2015 at 12:13:32PM +0530, Ajay Garg wrote:
> I started in the morning to build the driver from the source provided
> by the vendor, but it was written in the times of kernel-version 2.4,
> and I got hopelessly stuck.
The vendor driver is only for 2.4? Peter?
> Wanting to take a break, I reset my setup, and VERY strangely, what I
> now observe is ::
>
> a)
> I am NOT able to send anything from the embedded-system to
> putty-session (nothing appears at all on the putty session).
>
> b)
> Receive is working perfectly (anything I type in the putty-session is
> received fine in the embedded-application).
>
>
> Not sure what the hell is going on :(
Did you enable hardware flow control somewhere perhaps?
> Also, as per http://lxr.free-electrons.com/source/drivers/usb/serial/ch341.c?v=3.16,
> the particular serial-USB-adapter device is added into the id_table,
> so seems supported as per say.
That id was added by 82078234d402 ("USB: serial: ch341: New VID/PID for
CH341 USB-serial") in 2008, which claims that the driver supports both
old and new devices.
> Additionally, the message has changed to
>
> ###########################################################
> usb 2-2: device not accepting address 8, error -71
> ###########################################################
This still looks like a hardware issue to me. Specifically, this happens
before the ch341 driver is even involved.
> Completely lost :(
Try to see if you can get the device to work reliably with some other
driver (vendor driver or other OS) to rule out a broken device.
Thanks,
Johan
next prev parent reply other threads:[~2015-08-27 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:09 Likely issue with ch341 kernel-module/driver Ajay Garg
2015-08-26 17:04 ` Johan Hovold
2015-08-26 18:09 ` Peter Stuge
2015-08-26 18:15 ` Johan Hovold
2015-08-27 6:43 ` Ajay Garg
2015-08-27 7:37 ` Johan Hovold [this message]
2015-08-27 8:27 ` Ajay Garg
2015-08-27 9:45 ` Johan Hovold
2015-08-27 12:03 ` Peter Stuge
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=20150827073759.GC32712@localhost \
--to=johan@kernel.org \
--cc=ajaygargnsit@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter@stuge.se \
/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