Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1214499

Re: Likely issue with ch341 kernel-module/driver

From Peter Stuge <peter@stuge.se>
Newsgroups linux.kernel
Subject Re: Likely issue with ch341 kernel-module/driver
Date 2015-08-27 14:10 +0200
Message-ID <q24ae-3Zi-27@gated-at.bofh.it> (permalink)
References (1 earlier) <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> <q1ZWV-6e9-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Johan Hovold 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?

http://www.wch.cn/download/CH341SER_LINUX_ZIP.html
http://www.wch.cn/downfile/177

The vendor driver version 1.2 readme.txt from 2014-10-10 says:

Current Driver support versions of linux kernel range from 2.6.25 to 3.13.x

It didn't build immediately against the kernel I had at hand, but with
a small touchup (patch attached) it built fine against a 3.10 kernel.


> > 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.

My hardware has that same VID/PID, but there is a version request
sent to the device and my version number is quite a bit higher (20-30)
than what is mentioned in the in-tree driver comments; I guess the
protocol grew with newer versions of the device, but VID/PID weren't
updated. I'm sure it's possible to have a backwards-compatible
driver, but the vendor driver differs enough from the in-tree driver
that I can't be confident that simply doing what the vendor driver
does will work also on older versions of the device.


> > ###########################################################
> > 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.

I haven't seen any messages like this with my hardware.


//Peter

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


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