From: Johan Hovold <johan@kernel.org>
To: Peter Stuge <peter@stuge.se>
Cc: Johan Hovold <johan@kernel.org>,
Ajay Garg <ajaygargnsit@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Likely issue with ch341 kernel-module/driver
Date: Wed, 26 Aug 2015 20:15:05 +0200 [thread overview]
Message-ID: <20150826181505.GA32712@localhost> (raw)
In-Reply-To: <20150826180930.21386.qmail@stuge.se>
On Wed, Aug 26, 2015 at 08:09:30PM +0200, Peter Stuge wrote:
> Johan Hovold wrote:
> > On Wed, Aug 26, 2015 at 09:39:36PM +0530, Ajay Garg wrote:
> ..
> > > garbage characters transmitted from embedded-device
> ..
> > > It seems that there is some issue with the driver.
> >
> > Why do think it's a driver issue?
>
> I can confirm similar issues with the in-tree driver and my hardware.
What hardware is that?
> > > Any chance this can be made to work?
>
> Ajay, please try building the vendor driver. That works well for me.
Yes, please do.
> > > Any upgrade that might solve the issue?
>
> There is no upgrade. Someone needs to spend a day or so on adding
> functionality from the vendor driver to the in-tree driver, in a
> backwards-compatible way.
>
> > Looks like a hardware issue, I'm afraid.
>
> When I got garbage from the in-tree driver it was indeed a driver issue.
That's good to hear. Care to write up a patch? :)
Thanks,
Johan
next prev parent reply other threads:[~2015-08-26 18:15 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 [this message]
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
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=20150826181505.GA32712@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.