public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: andrew may <acmay@acmay•homeip.net>
To: Tom Rini <trini@kernel•crashing.org>
Cc: andrew may <acmay@acmay•homeip.net>, Armin <akuster@pacbell•net>,
	John Tyner <jtyner@cs•ucr.edu>,
	linuxppc-embedded@lists•linuxppc.org
Subject: Re: [PATCH] early serial init
Date: Thu, 11 Apr 2002 16:28:49 -0700	[thread overview]
Message-ID: <20020411162849.F18158@ecam.san.rr.com> (raw)
In-Reply-To: <20020411231056.GJ759@opus.bloom.county>


On Thu, Apr 11, 2002 at 04:10:56PM -0700, Tom Rini wrote:
> On Thu, Apr 11, 2002 at 03:36:42PM -0700, andrew may wrote:
>
> > This patch is to remove the need for the BASE BAUD define.
>
> Only if you get this information from somewhere else, yes?  This isn't
> currently something we grab from OpenBIOS, or could, right?

If you look at the patch you see the only thing we need to know is the clock
rate of the CPU. Then you can to a mfdcr() to calc the base baud. If there
is an external clock then we need the basebaud from somewhere else.

We dumped OpenBIOS and put on PPCBoot, but I think OpenBIOS provides the
clock speed.

> > If we ever start
> > trying to get a single kernel to build for multiple 405 boards that run at
> > various clock rates it becomes helpful to calc the base baud for the serial
> > ports rather than forcing it at compile time.
>
> If we ever start trying to get a single kernel to build for multiple 405
> boards something has gone wrong. :)
>
> More seriously, if someone wants to try and do that there's lots of
> other things which would need to be changed first.

Yes there is a lot of work to do, but I would like to see it happen.
Right now we have to do seperate builds for our custum board and one for
our Walnut boards and that is a pain.

I though it would be good to start small and see how things go, before another
fork got started :).

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

  reply	other threads:[~2002-04-11 23:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11 20:00 [PATCH] early serial init John Tyner
2002-04-11 14:20 ` Armin
2002-04-11 21:26   ` John Tyner
2002-04-11 14:53     ` Armin
2002-04-11 22:36       ` andrew may
2002-04-11 16:05         ` Armin
2002-04-11 23:18           ` andrew may
2002-04-11 22:43         ` Matthew Locke
2002-04-11 22:52           ` John Tyner
2002-04-11 22:54         ` Matthew Locke
2002-04-11 23:10         ` Tom Rini
2002-04-11 23:28           ` andrew may [this message]
2002-04-12  0:03             ` Tom Rini
2002-04-12  0:41               ` andrew may
2002-04-11 23:09       ` Tom Rini
2002-04-12  1:29         ` David Gibson

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=20020411162849.F18158@ecam.san.rr.com \
    --to=acmay@acmay$(echo .)homeip.net \
    --cc=akuster@pacbell$(echo .)net \
    --cc=jtyner@cs$(echo .)ucr.edu \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=trini@kernel$(echo .)crashing.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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