linux-kernel - Re: Likely issue with ch341 kernel-module/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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 27 Aug 2015 13:57:01 +0530
From:	Ajay Garg <ajaygargnsit@...il.com>
To:	Johan Hovold <johan@...nel.org>
Cc:	Peter Stuge <peter@...ge.se>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: Likely issue with ch341 kernel-module/driver

Hi John.

On Thu, Aug 27, 2015 at 1:07 PM, Johan Hovold <johan@...nel.org> wrote:
>
> 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.
>

I tested the serial-usb adapter using a loopback-hardware-tool
(confirmed to be perfect).
Using this, I see what I type, echo it back, and see what I receive.

The putty session-settings are standard one - 9600, 8N-1, no parity.

The byte flow is
putty-on-laptop => usb-interface => serial-interface => loopback =>
serial-interface => usb-interface => putty-on-laptop.

Thereafter, following are the echo-sequences I see ::

a ==> 0
b ==> '
c ==> N

This (I guess) confirms a problem on (at least) the driver-side.

Thanks everyone for the quick replies so far, I am grateful.

Thanks and Regards,
Ajay
--
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/