All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org
Subject: Re: CH341 driver and the 5.4 kernel
Date: Wed, 7 Jul 2021 17:55:36 -0400	[thread overview]
Message-ID: <CAH8yC8mZ1J9QZyZPfpsKdJ0NmfbACZOcUqzZ5EGWkyDoGddeFA@mail.gmail.com> (raw)
In-Reply-To: <20210707144525.GA177599@rowland.harvard.edu>

On Wed, Jul 7, 2021 at 10:45 AM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Wed, Jul 07, 2021 at 03:33:52AM -0400, Jeffrey Walton wrote:
> > Hi Everyone,
> >
> > I'm trying to track down the cause of some garbage in a response when
> > using an ELM327 (https://www.elmelectronics.com/ic/elm327/) with a
> > CH341 serial controller.
> >
> > I see there's been a fair amount of activity with the CH341
> > (https://github.com/torvalds/linux/commits/master/drivers/usb/serial/ch341.c),
> > but I can't tell if its been backported to the 5.4 kernel.
> > Specifically, the 5.4.0-77 kernel supplied with Ubuntu 18.04 and Mint
> > 20.1.
> >
> > Does anyone know if the fixes and improvements for the CH341 have made
> > their way into the 5.4 kernel?
>
> If you're talking about the 5.4.y kernels from kernel.org (as opposed
> to the kernels supplied by Ubuntu, which might have goodness knows
> what in them), you can see for yourself easily enough:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/usb/serial/ch341.c?h=linux-5.4.y

Thanks Alan.

As far as I know, Ubuntu uses -oem kernels that track upstream. All
upstream changes should be merged into Ubuntu's gear. Also see
https://wiki.ubuntu.com/Kernel/OEMKernel.

Jeff

  reply	other threads:[~2021-07-07 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07  7:33 CH341 driver and the 5.4 kernel Jeffrey Walton
2021-07-07  7:41 ` Greg KH
2021-07-07  7:56   ` Jeffrey Walton
2021-07-07 10:46     ` Greg KH
2021-07-07 14:45 ` Alan Stern
2021-07-07 21:55   ` Jeffrey Walton [this message]
2021-07-07 21:48 ` Jeffrey Walton
2021-07-08  6:17   ` Greg KH

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=CAH8yC8mZ1J9QZyZPfpsKdJ0NmfbACZOcUqzZ5EGWkyDoGddeFA@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.