public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: hpa@zytor.com
Cc: linux-serial@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>, Johan Hovold <johan@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: Insanely high baud rates
Date: Thu, 11 Oct 2018 13:31:34 +0100	[thread overview]
Message-ID: <20181011133134.085624af@alans-desktop> (raw)
In-Reply-To: <16D6AB22-697E-498C-A5B2-3AD90B567E86@zytor.com>

> I'm mostly wondering if it is worth future-proofing for new transports. It sounds like we can have a consensus on leaving the upper 4 bits of the speed fields reserved, but leave the details of implementation for the future?

It seems reasonable, although I think the reality is that any future
transport is not going to be a true serial link, but some kind of serial
emulation layer. For those the speed really only matters to tell editors
and the like not to bother being clever.

I mean - what is the baud rate of a pty  ?

Alan

  reply	other threads:[~2018-10-11 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 19:19 Insanely high baud rates H. Peter Anvin
2018-10-09 19:51 ` Willy Tarreau
2018-10-09 20:02   ` H. Peter Anvin
2018-10-10 20:17 ` Alan Cox
2018-10-10 20:20   ` hpa
2018-10-11 12:31     ` Alan Cox [this message]
2018-10-11 14:14       ` hpa
2018-10-11 21:40         ` Theodore Y. Ts'o
2018-10-12  5:48           ` H. Peter Anvin
2018-10-11 19:36       ` Craig Milo Rogers
2018-10-11 19:39         ` H. Peter Anvin

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=20181011133134.085624af@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=johan@kernel.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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