← Back to team overview

kernel-packages team mailing list archive

[Bug 1591226] Re: ch341 usb serial converter kernel driver parity patch missing


Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name <email>), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: Confirmed => Triaged

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  ch341 usb serial converter kernel driver parity patch missing

Status in linux package in Ubuntu:

Bug description:
  I have several pieces of this cheap Chinese USB2serial port converter,
  which uses ch341.ko kernel module.

  By default / fault, the parity function of this chip is not implemented in the kernel driver.
  This causes that the converter is UNUSABLE on ubuntu linux 14.04 (latest updates installed, default kernel, current version 3.13.0-88-generic)
  There is a fix for that, applying that patch makes it work as it should be. 

  All current ubuntu kernels miss this patch:

  I have to recompile the kernel module ch341.ko every time when new kernel version is installed.
  It seems to me while googling this, that somehow this fix haven't got into mainstream kernel.

  Please include this patch to all ubuntu kernel versions!
  Thank you!
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
   /dev/snd/controlC1:  narancs    3260 F.... pulseaudio
   /dev/snd/controlC0:  narancs    3260 F.... pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=79d5ef01-c38c-44d6-9371-52cb0adb988e
  InstallationDate: Installed on 2014-12-14 (546 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  MachineType: Hewlett-Packard HP ZBook 15
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-88-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
   linux-restricted-modules-3.13.0-88-generic N/A
   linux-backports-modules-3.13.0-88-generic  N/A
   linux-firmware                             1.127.22
  Tags:  trusty
  Uname: Linux 3.13.0-88-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L70 Ver. 01.08
  dmi.board.name: 1909
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.08:bd04/10/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DC10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.51:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15
  dmi.product.version: A3009DC10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

Follow ups