From: Greg KH <gregkh@linuxfoundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Maarten Brock <Maarten.Brock@sttls.nl>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Serial port DTR/RTS - O_NRESETDEV
Date: Wed, 12 Nov 2025 11:46:50 -0500 [thread overview]
Message-ID: <2025111241-domestic-moonstone-f75f@gregkh> (raw)
In-Reply-To: <6DBB5931-ACD4-4174-9FCE-96C45FFC4603@zytor.com>
On Wed, Nov 12, 2025 at 08:09:45AM -0800, H. Peter Anvin wrote:
> On November 12, 2025 3:22:56 AM PST, Greg KH <gregkh@linuxfoundation.org> wrote:
> >On Mon, Nov 10, 2025 at 07:57:22PM -0800, H. Peter Anvin wrote:
> >> Honestly, though, I'm far less interested in what 8250-based hardware does than e.g. USB.
> >
> >hahahahahahaha {snort}
> >
> >Hah. that's a good one.
> >
> >Oh, you aren't kidding.
> >
> >Wow, good luck with this. USB-serial adaptors are all over the place,
> >some have real uarts in them (and so do buffering in the device, and
> >line handling in odd ways when powered up), and some are almost just a
> >straight pipe through to the USB host with control line handling ideas
> >tacked on to the side as an afterthought, if at all.
> >
> >There is no standard here, they all work differently, and even work
> >differently across the same device type with just barely enough hints
> >for us to determine what is going on.
> >
> >So don't worry about USB, if you throw that into the mix, all bets are
> >off and you should NEVER rely on that.
> >
> >Remeber USB->serial was explicitly rejected by the USB standard group,
> >only to have it come back in the "side door" through the spec process
> >when it turned out that Microsoft hated having to write a zillion
> >different vendor-specific drivers because the vendor provided ones kept
> >crashing user's machines. So what we ended up with was "just enough" to
> >make it through the spec process, and even then line signals are
> >probably never tested so you can't rely on them.
> >
> >good luck!
> >
> >greg "this brought up too many bad memories" k-h
>
> Ugh.
>
> I have made it very clear that I am very aware that there is broken hardware.
I would posit that there is NO "non-broken" usb->serial devices out
there. The closest I have seen was the old IO-Edgeport devices, but
they were expensive and got bought out by some other company and in the
end didn't succeed due to all of the "cheap" devices/chips out there
that just did dumb tx/rx transfers over a fake serial connection.
> What I'm trying to do is to deal with the (occasional) case of
> *non*-broken hardware. Right now Linux breaks the non-broken hardware
> for it, and I don't think the existence of broken hardware is a good
> justification for that.
No, but we have to handle both somehow.
And given that we still get brand-new UART drivers sent to use every few
months, there is just more and more "broken" hardware out there overall.
Anyway, good luck coming up with a scheme to handle your crazy
connections, I would push back and say "any device that treats a serial
control line as a power signal is broken to start with" :)
greg k-h
next prev parent reply other threads:[~2025-11-12 17:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 7:53 RFC: Serial port DTR/RTS - O_NRESETDEV H. Peter Anvin
2025-11-07 17:37 ` Theodore Ts'o
2025-11-09 2:25 ` H. Peter Anvin
2025-11-10 3:35 ` Theodore Ts'o
2025-11-10 5:00 ` H. Peter Anvin
2025-11-10 10:06 ` Maarten Brock
2025-11-10 20:19 ` Theodore Ts'o
2025-11-10 21:05 ` H. Peter Anvin
2025-11-11 3:51 ` Theodore Ts'o
2025-11-11 3:57 ` H. Peter Anvin
2025-11-11 4:38 ` Theodore Ts'o
2025-11-11 10:21 ` Maarten Brock
2025-11-11 21:28 ` H. Peter Anvin
2025-11-12 11:22 ` Greg KH
2025-11-12 16:09 ` H. Peter Anvin
2025-11-12 16:46 ` Greg KH [this message]
2025-11-12 19:12 ` H. Peter Anvin
2025-11-12 19:39 ` Greg KH
2025-11-12 19:53 ` H. Peter Anvin
2025-11-12 19:55 ` H. Peter Anvin
2025-11-13 22:24 ` RFC: Serial port DTR/RTS - O_<something> H. Peter Anvin
2025-11-14 10:26 ` Maarten Brock
2025-11-14 18:49 ` Maciej W. Rozycki
2025-11-14 18:53 ` H. Peter Anvin
2025-11-15 21:29 ` Ned Ulbricht
2025-11-15 22:29 ` H. Peter Anvin
2025-11-16 0:47 ` H. Peter Anvin
2025-11-18 16:33 ` Ned Ulbricht
2025-11-18 17:31 ` H. Peter Anvin
2025-11-18 18:05 ` H. Peter Anvin
2025-11-20 13:31 ` Ned Ulbricht
2025-11-10 5:20 ` RFC: Serial port DTR/RTS - O_NRESETDEV H. Peter Anvin
2025-11-09 20:43 ` Maciej W. Rozycki
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=2025111241-domestic-moonstone-f75f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Maarten.Brock@sttls.nl \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).