From: Oliver Neukum <oneukum@suse.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: ttyACM: disabled by hub (EMI?), re-enabling... Causes garbage chars & disconnect
Date: Mon, 08 Jun 2020 21:21:28 +0200 [thread overview]
Message-ID: <1591644088.24937.7.camel@suse.com> (raw)
In-Reply-To: <294b2e8330b8c04652ffbab7829dd2cbfa2cf081.camel@infinera.com>
Am Montag, den 08.06.2020, 16:00 +0000 schrieb Joakim Tjernlund:
> User space already does this, but the automatic ECHOing that happens at open
> is not possible to address in user space. The buffered chars are sent to both
> the terminal app(putty/minicom etc.) and over the wire to the shell waiting there
> and that is the problem. There is no way to prevent that ECHO back over the wire(USB)
> as the default is to ECHO and one have to open the tty to change to non ECHO.
Hi,
this is correct, but not specific to CDC-ACM. Could you ask the serial
maintainers and look at what SUS respectively POSIX have to say about
correct behavior?
Regards
Oliver
next prev parent reply other threads:[~2020-06-08 19:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 14:46 ttyACM: disabled by hub (EMI?), re-enabling... Causes garbage chars & disconnect Joakim Tjernlund
2020-05-25 15:02 ` Oliver Neukum
2020-05-25 15:15 ` Joakim Tjernlund
2020-05-25 16:49 ` Joakim Tjernlund
2020-05-26 8:47 ` Oliver Neukum
2020-05-26 8:59 ` Joakim Tjernlund
2020-05-26 10:14 ` Oliver Neukum
2020-05-26 16:46 ` Joakim Tjernlund
2020-05-26 17:19 ` Joakim Tjernlund
2020-05-27 8:38 ` Oliver Neukum
2020-05-27 9:40 ` Joakim Tjernlund
2020-05-27 10:12 ` Greg KH
2020-05-27 10:41 ` Oliver Neukum
2020-05-27 13:16 ` Joakim Tjernlund
2020-05-27 15:41 ` Joakim Tjernlund
2020-06-05 10:09 ` Joakim Tjernlund
2020-06-08 9:13 ` Oliver Neukum
2020-06-08 11:39 ` Joakim Tjernlund
2020-06-08 15:40 ` Oliver Neukum
2020-06-08 16:00 ` Joakim Tjernlund
2020-06-08 19:21 ` Oliver Neukum [this message]
2020-06-15 11:01 ` Joakim Tjernlund
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=1591644088.24937.7.camel@suse.com \
--to=oneukum@suse.com \
--cc=Joakim.Tjernlund@infinera.com \
--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.