All of lore.kernel.org
 help / color / mirror / Atom feed
From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] My GT-64260 enhancements
Date: Sun, 17 Mar 02 10:16:02 PST	[thread overview]
Message-ID: <0203171816.AA01595@ivan.Harhan.ORG> (raw)


Dan Malek <dan@embeddededge.com> wrote:

> 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.

But if you don't specify the baud rate in any way, it'll default to 9600 except
on the EV-64260-BP.

Also I don't like calling the standard serial console "debug". A standard
computer running UNIX or a UNIX-like system must have a standard serial port as
the console for root to do sysadmin work, not a PeeCee video/keyboard. Just
like every standard VAX.

> It shouldn't be a hard-coded value.  It should at least be the standard Linux
> command line option.

That option works of course. I'm simply asking to remove the line from
arch/ppc/config.in that makes the EV-64260-BP port have a different default
from the rest of Linux, which I claim is inappropriate.

> Bootloaders should simply use the port as it was
> configured by the boot rom.

I'm not talking about any bootloader, I'm talking about the kernel (vmlinux).
My bootloader (ppc-linux-boot) doesn't know anything about UARTs at all, it
makes console user services calls to the firmware ROM to talk to the abstract
console device.

MS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-03-17 18:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-17 18:16 Michael Sokolov [this message]
2002-03-17 18:42 ` [PATCH] My GT-64260 enhancements Dan Malek
2002-03-17 20:10   ` Michael Sokolov
2002-03-18 14:54     ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2002-03-20  0:46 Michael Sokolov
2002-03-19 22:55 ` Mark A. Greer
2002-03-15  6:11 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
2002-03-18 15:00         ` Tom Rini
2002-03-18 15:53       ` [Linux-galileo] " Mark A. Greer
2002-03-18 18:48         ` Tom Rini

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=0203171816.AA01595@ivan.Harhan.ORG \
    --to=msokolov@ivan.harhan.org \
    --cc=linux-galileo@source.mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.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.