Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1214367
| From | Johan Hovold <johan@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Likely issue with ch341 kernel-module/driver |
| Date | 2015-08-27 09:40 +0200 |
| Message-ID | <q1ZWV-6e9-5@gated-at.bofh.it> (permalink) |
| References | <q1LqV-2d7-13@gated-at.bofh.it> <q1Mn1-3z4-23@gated-at.bofh.it> <q1Nj4-4Uz-5@gated-at.bofh.it> <q1NsK-55Y-25@gated-at.bofh.it> <q1Zay-524-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[ 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Likely issue with ch341 kernel-module/driver Ajay Garg <ajaygargnsit@gmail.com> - 2015-08-26 18:10 +0200
Re: Likely issue with ch341 kernel-module/driver Johan Hovold <johan@kernel.org> - 2015-08-26 19:10 +0200
Re: Likely issue with ch341 kernel-module/driver Peter Stuge <peter@stuge.se> - 2015-08-26 20:10 +0200
Re: Likely issue with ch341 kernel-module/driver Johan Hovold <johan@kernel.org> - 2015-08-26 20:20 +0200
Re: Likely issue with ch341 kernel-module/driver Ajay Garg <ajaygargnsit@gmail.com> - 2015-08-27 08:50 +0200
Re: Likely issue with ch341 kernel-module/driver Johan Hovold <johan@kernel.org> - 2015-08-27 09:40 +0200
Re: Likely issue with ch341 kernel-module/driver Ajay Garg <ajaygargnsit@gmail.com> - 2015-08-27 10:30 +0200
Re: Likely issue with ch341 kernel-module/driver Johan Hovold <johan@kernel.org> - 2015-08-27 11:50 +0200
Re: Likely issue with ch341 kernel-module/driver Peter Stuge <peter@stuge.se> - 2015-08-27 14:10 +0200
csiph-web