All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:45:49 +0200	[thread overview]
Message-ID: <20150827094549.GB3552@localhost> (raw)
In-Reply-To: <CAHP4M8XrAH7nefdOWE2JfWh0GZMwvA_FSz=E+PCW52zwqFj8LA@mail.gmail.com>

On Thu, Aug 27, 2015 at 01:57:01PM +0530, Ajay Garg wrote:
> Hi John.
> 
> On Thu, Aug 27, 2015 at 1:07 PM, Johan Hovold <johan@kernel.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.

Not unless you confirm that the same setup works when using a different
driver, right? Otherwise, it could still be a hw issue.

Johan

  reply	other threads:[~2015-08-27  9:45 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
2015-08-27  8:27           ` Ajay Garg
2015-08-27  9:45             ` Johan Hovold [this message]
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=20150827094549.GB3552@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.