From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208959] New: USB-serial (mct_u232): bit7=1 when tty is set to cs7?
Date: Wed, 19 Aug 2020 02:52:47 +0000 [thread overview]
Message-ID: <bug-208959-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208959
Bug ID: 208959
Summary: USB-serial (mct_u232): bit7=1 when tty is set to cs7?
Product: Drivers
Version: 2.5
Kernel Version: 5.7.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: mslade@epic-code.com.au
Regression: No
I'm not 100% certain this is a bug, please let me know if this is expected
behavior.
I have hooked an old serial mouse up to a USB serial device, USB ID 0711:0230
(part of an circa 2000 Targus port replicator)
when I configure it with the appropriate 1200 baud and 7 bit char width, the
bytes that come through /dev/ttyUSB0 all have bit7 set to 1.
This behavior is in contrast to an old serial port on a box running a 2.4.19
kernel.
Is there a standard for the value that non-data bits should be set to?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-08-19 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 2:52 bugzilla-daemon [this message]
2020-08-24 8:42 ` [Bug 208959] New: USB-serial (mct_u232): bit7=1 when tty is set to cs7? 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
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@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.