Date: Wed, 26 Aug 2015 20:15:05 +0200
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
Message-ID: <20150826181505.GA32712@localhost>
References: <CAHP4M8X3yC8tC-=pEt2wMqO_S7nrELAGMOVY5aTf73AEup9qOQ@mail.gmail.com>
 <20150826170440.GB28324@localhost>
 <20150826180930.21386.qmail@stuge.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150826180930.21386.qmail@stuge.se>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1199
Lines: 39

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