linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: andrew may <acmay@acmay.homeip.net>
To: Armin <akuster@pacbell.net>
Cc: andrew may <acmay@acmay.homeip.net>,
	John Tyner <jtyner@cs.ucr.edu>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] early serial init
Date: Thu, 11 Apr 2002 16:18:37 -0700	[thread overview]
Message-ID: <20020411161837.E18158@ecam.san.rr.com> (raw)
In-Reply-To: <3CB5B452.3080603@pacbell.net>


On Thu, Apr 11, 2002 at 04:05:38PM +0000, Armin wrote:
> This patch did not remove BASE_BAUD from the headers??? Having an option
> for early boot is a good thing, this patch removes that option.  Your
> patch would only affect the walnut?  David's is at least in setup.c
> where more boards have access to the early serial init code.

This patch was more a proof of concept. I need it on our devel board that
may run at different speeds. It becomes hard to find a good overall base baud
rate that will work for multiple clock speeds, that doesn't cause rounding
errors that throw off the final baud rate.

Since BASE_BAUD is defined in the platform section I though to put the code
in the same area. I did not look around for the best place to put it so setup.c
may be a better spot.

If a external serial clock is used the BaseBaud still needs to be correct.
So that is one reason not to remove the define completely, but for anything
that uses the internal clock BaseBaud could be set to 0.

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

  reply	other threads:[~2002-04-11 23:18 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 [this message]
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
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=20020411161837.E18158@ecam.san.rr.com \
    --to=acmay@acmay.homeip.net \
    --cc=akuster@pacbell.net \
    --cc=jtyner@cs.ucr.edu \
    --cc=linuxppc-embedded@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 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).