From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] TERM for v8
Date: Sun, 5 Nov 2017 13:28:18 -0600 [thread overview]
Message-ID: <3c04537a-70d3-e37f-017a-0e6439c199ec@gmail.com> (raw)
In-Reply-To: <20171105190037.71E88156E7D7@mail.bitblocks.com>
On 11/5/17 1:00 PM, Bakul Shah wrote:
> Based on the following snippet my guess is that the kernel
> doesn't report the right baud rate for the console.
>
>>>> # stty 9600
>>>> # stty
>>>> speed: 0 baud
Yeabut, it works fine on tty00 (the DZ):
# stty exta
# stty
speed: 19200 baud
...
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
next prev parent reply other threads:[~2017-11-05 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 4:05 Will Senn
2017-11-05 4:34 ` William Corcoran
2017-11-05 5:14 ` Will Senn
2017-11-05 5:44 ` Clem cole
2017-11-05 14:01 ` Will Senn
2017-11-05 18:04 ` Clem cole
2017-11-05 18:55 ` Will Senn
2017-11-05 19:00 ` Bakul Shah
2017-11-05 19:28 ` Will Senn [this message]
2017-11-05 19:43 ` Bakul Shah
2017-11-05 20:42 ` Paul Winalski
2017-11-06 16:21 ` Bakul Shah
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=3c04537a-70d3-e37f-017a-0e6439c199ec@gmail.com \
--to=will.senn@gmail.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;
as well as URLs for NNTP newsgroup(s).