All of
 help / color / mirror / Atom feed
From: Johan Hovold <>
To: Malte Bayer <>
Subject: Re: Possible bug in the cp210x kernel driver?
Date: Mon, 20 Sep 2021 10:10:42 +0200	[thread overview]
Message-ID: <YUhCAtQIE5vbD/> (raw)
In-Reply-To: <>

[ Adding linux-usb on CC ]

On Sat, Sep 18, 2021 at 03:49:22PM +0200, Malte Bayer wrote:
> Hello Johan,
> I recently had a problem with libdivecomputer fetching a specific dive
> log. After debugging the issue I tracked the problem down to the
> cp210x kernel driver.
> Last year, you submitted a change for "Line status events"
>  connection to my mares puck pro is established with even parity.
> Every time, the dive computer sends the byte pair 0xEC 0x00 (which in
> my case is valid transmitted data from the connected device to the
> pc), the 0x00 after the 0xEC gets dropped by the driver.
> For reference, please take a look on
> and jefdriesen's answer.
> libdivecomputer does raw reads of binary data - therefore I dont think
> that it's a good idea to manipulate the received data stream?

Thanks for the report.

In event mode the device is supposed to replace any '0xec' characters
in the input stream with the string '0xec 0x00', which the driver then
needs to convert back to '0xec'.

But clearly your device doesn't escape '0xec' as expected.

What type of cp210x are you using?

As you already discovered you can disable input parity checking (INPCK)
as a workaround meanwhile.


       reply	other threads:[~2021-09-20  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-09-20  8:10 ` Johan Hovold [this message]
     [not found] <>
2021-09-21  8:34 ` Johan Hovold
     [not found] <>
2021-09-22 11:28 ` Johan Hovold
2021-09-22 20:25   ` Malte Di Donato
2021-09-23  8:52     ` Johan Hovold

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YUhCAtQIE5vbD/ \ \ \ \
    --subject='Re: Possible bug in the cp210x kernel driver?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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.