From: David Monro <davidm@amberdata.demon.co.uk>
To: Dan Malek <dan@embeddededge.com>
Cc: Michael Sokolov <msokolov@ivan.Harhan.ORG>,
linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] My GT-64260 enhancements
Date: Sun, 17 Mar 2002 20:24:27 +0000 [thread overview]
Message-ID: <3C94FB7B.5040007@amberdata.demon.co.uk> (raw)
In-Reply-To: 3C94D78E.3010100@embeddededge.com
Dan Malek wrote:
>
> Michael Sokolov wrote:
>
>> But Troy's personal preferences shouldn't affect the public tree, should
>> they? If 9600 is the default baud rate for all of Linux, why
>> should one port be different?
>
>
> I didn't know there was a "default" baud rate for Linux. I think
> the lowest I have ever seen is 9600, but I certainly wouldn't call
> it a default. It seems every one of the boards I have uses
> something different,
>
The default for just about any unix box (and an awful lot of other
things - network switches etc) seems to be 9600 8N1, partly because even
ancient terminals can cope with that (a lot of older ones don't go past
38400 for example). Allowing an override is fine, but leaving the
default at 9600 will follow the 'path of least surprise'.
Cheers,
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-17 20:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 6:11 [PATCH] My GT-64260 enhancements Michael Sokolov
2002-03-15 17:04 ` Tom Rini
2002-03-16 8:21 ` Michael Sokolov
2002-03-16 15:15 ` Tom Rini
2002-03-17 7:03 ` Michael Sokolov
2002-03-17 17:51 ` Dan Malek
2002-03-17 20:24 ` David Monro [this message]
2002-03-18 15:00 ` Tom Rini
2002-03-18 15:53 ` [Linux-galileo] " Mark A. Greer
2002-03-18 18:48 ` Tom Rini
2002-03-15 20:05 ` [Linux-galileo] " Nye Liu
-- strict thread matches above, loose matches on Subject: below --
2002-03-17 18:16 Michael Sokolov
2002-03-17 18:42 ` Dan Malek
2002-03-17 20:10 ` Michael Sokolov
2002-03-18 14:54 ` Tom Rini
2002-03-20 0:46 Michael Sokolov
2002-03-19 22:55 ` Mark A. Greer
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=3C94FB7B.5040007@amberdata.demon.co.uk \
--to=davidm@amberdata.demon.co.uk \
--cc=dan@embeddededge.com \
--cc=linux-galileo@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.