From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: LILO and serial speeds over 9600
Date: 12 Feb 2001 10:51:46 -0800 [thread overview]
Message-ID: <969bc2$seh$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10102120741290.3761-100000@main.cyclades.com> <Pine.LNX.4.10.10102120849580.3761-100000@main.cyclades.com>
Followup to: <Pine.LNX.4.10.10102120849580.3761-100000@main.cyclades.com>
By author: Ivan Passos <lists@cyclades.com>
In newsgroup: linux.dev.kernel
>
> Since I still want to add support for speeds up to 115200, the other two
> questions are still up (see below):
>
Just checked my own code, and SYSLINUX does indeed support 115200 (I
changed this to be a 32-bit register ages ago, apparently.) Still
doesn't answer the question "why"... all I think you do is increase
the risk for FIFO overrun and lost characters (flow control on a boot
loader console is vestigial at the best.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
next prev parent reply other threads:[~2001-02-12 18:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 15:45 LILO and serial speeds over 9600 Ivan Passos
2001-02-12 16:53 ` Ivan Passos
2001-02-12 18:47 ` H. Peter Anvin
2001-02-12 20:39 ` James Sutherland
2001-02-12 20:54 ` H. Peter Anvin
2001-02-12 22:55 ` James Sutherland
2001-02-14 11:45 ` Pavel Machek
2001-02-12 21:52 ` Alan Cox
2001-02-12 22:10 ` H. Peter Anvin
2001-02-12 22:25 ` Alan Cox
2001-02-12 23:11 ` Werner Almesberger
2001-02-12 23:16 ` Alan Cox
2001-02-12 23:20 ` H. Peter Anvin
2001-02-12 23:27 ` Alan Cox
2001-02-12 23:53 ` H. Peter Anvin
2001-02-13 0:11 ` Alan Cox
2001-02-13 0:17 ` Tim Wright
2001-02-13 0:23 ` H. Peter Anvin
2001-02-13 10:51 ` Alan Cox
2001-02-13 10:57 ` James Sutherland
2001-02-13 12:55 ` Russell King
2001-02-13 13:56 ` James Sutherland
2001-02-13 0:25 ` H. Peter Anvin
2001-02-12 23:35 ` James Sutherland
2001-02-12 23:51 ` H. Peter Anvin
2001-02-13 0:24 ` James Sutherland
2001-02-13 0:27 ` H. Peter Anvin
2001-02-12 23:19 ` H. Peter Anvin
2001-02-12 23:23 ` Alan Cox
2001-02-14 11:53 ` Pavel Machek
2001-02-17 17:26 ` Patrick Michael Kane
2001-02-17 17:40 ` James Sutherland
2001-02-21 3:11 ` Network console project (was: LILO and serial speeds over 9600) H. Peter Anvin
2001-02-21 9:29 ` Network console project Jan-Benedict Glaw
2001-02-22 21:52 ` Network console project (was: LILO and serial speeds over 9600) Pavel Machek
2001-02-23 15:54 ` Andreas Dilger
2001-02-12 22:46 ` LILO and serial speeds over 9600 James Sutherland
2001-02-12 22:50 ` Alan Cox
2001-02-12 18:51 ` H. Peter Anvin [this message]
2001-02-12 19:49 ` Scott Laird
2001-02-12 23:17 ` Ivan Passos
2001-02-12 23:30 ` Chris Wedgwood
2001-02-12 23:39 ` David Weinehall
2001-02-13 2:52 ` Michael Rothwell
[not found] <Pine.LNX.4.21.0102131506230.30955-100000@lefty.dyndns.org>
2001-02-13 6:12 ` 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='969bc2$seh$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox