From: Armin <akuster@pacbell.net>
To: andrew may <acmay@acmay.homeip.net>
Cc: John Tyner <jtyner@cs.ucr.edu>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] early serial init
Date: Thu, 11 Apr 2002 16:05:38 +0000 [thread overview]
Message-ID: <3CB5B452.3080603@pacbell.net> (raw)
In-Reply-To: 20020411153642.C18158@ecam.san.rr.com
andrew may wrote:
> On Thu, Apr 11, 2002 at 02:53:36PM +0000, Armin wrote:
>
>>John Tyner wrote:
>>
>>>I remember seeing something awhile ago about early boots, but I didn't
>>>think it was for Walnut. Where is it/would it be?
>>>
>>>On Thu, 11 Apr 2002, Armin wrote:
>>>
>>>
>>>
>>>>John Tyner wrote:
>>>>
>>>>
>>
>>David G did something and he hit the head_4xx.S & ppc4xx_setup.c and a
>>few header files imb405gp.h
>>
>
> This patch is to remove the need for the BASE BAUD define. 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.
>
>
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.
armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-11 16:05 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 [this message]
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
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=3CB5B452.3080603@pacbell.net \
--to=akuster@pacbell.net \
--cc=acmay@acmay.homeip.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).