All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208959] USB-serial (mct_u232): bit7=1 when tty is set to cs7?
Date: Wed, 26 Aug 2020 07:08:34 +0000	[thread overview]
Message-ID: <bug-208959-208809-QRee3s7U7H@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208959-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=208959

--- Comment #3 from Johan Hovold (johan@kernel.org) ---
On Tue, Aug 25, 2020 at 03:20:48PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208959
> 
> --- Comment #2 from mslade@epic-code.com.au (mslade@epic-code.com.au) ---
> Please clarify what you mean by "converter" here.

I was referring to the USB-serial device.

> FYI to test I was just doing this:
> 
> # stty -F /dev/ttyUSB0 1200 cs7

What is the output of "stty -a -F /dev/ttyUSB0" after this?

> # dd if=/dev/ttyUSB0 bs=1|hd

Try using a terminal program instead and connect the device to another
USB-serial device (e.g. ftdi or pl2303) and see if you can get 7-bit
words to work.

You can also try enabling debugging and provide the relevant bits from
dmesg when you connect, configure and read from the device:

        echo module mct_u232 +p > /sys/kernel/debug/dynamic_debug/control

Johan

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2020-08-26  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19  2:52 [Bug 208959] New: USB-serial (mct_u232): bit7=1 when tty is set to cs7? bugzilla-daemon
2020-08-24  8:42 ` Johan Hovold
2020-08-24  8:42 ` [Bug 208959] " bugzilla-daemon
2020-08-25 15:20 ` bugzilla-daemon
2020-08-26  7:08   ` Johan Hovold
2020-08-26  7:08 ` bugzilla-daemon [this message]

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=bug-208959-208809-QRee3s7U7H@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.