From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: Vojtech Pavlik <vojtech@suse.com>,
Oliver Neukum <oneukum@suse.com>,
linux-usb@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: Re: ttyACM versus ttyUSB
Date: Mon, 13 Oct 2025 18:14:25 +0200 [thread overview]
Message-ID: <2025101339-snowbound-capsule-fc4a@gregkh> (raw)
In-Reply-To: <CAMMLpeTZxLCK2sh0qpHoFzHCrntc-vLSWqJJUjicS2xRR2AdNw@mail.gmail.com>
On Mon, Oct 13, 2025 at 09:42:38AM -0600, Alex Henrie wrote:
> > Today, some USB-serial chips have the ACM protocol, so perhaps it would
> > make sense to merge the drivers, I certainly would not object.
>
> It is definitely confusing to have to think about whether your USB
> serial device is going to appear as /dev/ttyUSB* or /dev/ttyACM*. On
> the other hand, if we renamed the ttyACM device nodes to ttyUSB to
> reflect the fact that ACM is just another USB serial protocol, how
> many things would that break? In general I like making things make
> sense, but I'm hesitant to be the one to pull the trigger.
Yeah, we can't really do that now, sorry. Too many chances to break
userspace.
If you want to always get this right, just use the symlinks in
/dev/serial/ to find the proper device easier.
greg k-h
prev parent reply other threads:[~2025-10-13 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 5:00 ttyACM versus ttyUSB Alex Henrie
2025-10-12 6:07 ` Greg KH
2025-10-12 15:55 ` Alex Henrie
2025-10-12 16:21 ` Greg KH
2025-10-12 19:01 ` Alex Henrie
2025-10-12 19:53 ` Greg KH
2025-10-12 22:40 ` Alex Henrie
2025-10-13 9:28 ` Oliver Neukum
2025-10-13 10:47 ` Vojtech Pavlik
2025-10-13 15:42 ` Alex Henrie
2025-10-13 16:14 ` Greg KH [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=2025101339-snowbound-capsule-fc4a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexhenrie24@gmail.com \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=vojtech@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox