From: Dan Malek <dan@embeddededge.com>
To: Michael Sokolov <msokolov@ivan.Harhan.ORG>
Cc: linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] My GT-64260 enhancements
Date: Sun, 17 Mar 2002 12:51:10 -0500 [thread overview]
Message-ID: <3C94D78E.3010100@embeddededge.com> (raw)
In-Reply-To: 0203170703.AA00587@ivan.Harhan.ORG
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 debug console serial port rates are either provided by passing some
bootloader information to the kernel or by a kernel command line option.
Either one is locally configurable.
> .... Who is the maintainer with authority over this? Would s/he accept a
> patch to axe that 115200 line out?
It shouldn't be a hard-coded value. It should at least be the standard Linux
command line option. Bootloaders should simply use the port as it was
configured by the boot rom.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-17 17:51 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 [this message]
2002-03-17 20:24 ` David Monro
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=3C94D78E.3010100@embeddededge.com \
--to=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 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).