From: Eugene Surovegin <ebs@ebshome.net>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] ppc32: cleanup AMCC PPC4xx eval boards to better support U-Boot
Date: Fri, 16 Sep 2005 09:27:33 -0700 [thread overview]
Message-ID: <20050916162733.GA8019@gate.ebshome.net> (raw)
In-Reply-To: <200509161306.17103.sr@denx.de>
On Fri, Sep 16, 2005 at 01:06:16PM +0200, Stefan Roese wrote:
> Add U-Boot support to AMCC PPC405 eval boards (bubinga, sycamore and walnut)
> and cleanup PPC440 eval boards (bamboo, ebony, luan and ocotea) to better
> support U-Boot as bootloader.
In general, 44x pieces look OK, but 40x aren't. Notice, that we don't
have any #ifdef CONFIG_UBOOT in 44x sources. Let's not add them for
40x, try to replicate the same boot-wrapper approach as Matt used for
44x.
[snip]
> diff --git a/arch/ppc/platforms/4xx/Kconfig b/arch/ppc/platforms/4xx/Kconfig
> --- a/arch/ppc/platforms/4xx/Kconfig
> +++ b/arch/ppc/platforms/4xx/Kconfig
> @@ -212,10 +212,18 @@ config EMBEDDEDBOOT
> depends on EP405 || XILINX_ML300
> default y
>
> -config IBM_OPENBIOS
> - bool
> +choice
> + prompt "Bootloader support"
> depends on ASH || BUBINGA || REDWOOD_5 || REDWOOD_6 || SYCAMORE || WALNUT
> - default y
> + default IBM_OPENBIOS
> +
> +config IBM_OPENBIOS
> + bool "IBM OpenBIOS"
> +
> +config UBOOT
> + bool "U-Boot"
> +
> +endchoice
Do we really need this? U-Boot build is different from OpenBIOS
already (we just use vmlinux without any boot-wrapper) and is selected
by different make target.
[snip]
> --- a/arch/ppc/platforms/4xx/bubinga.c
> +++ b/arch/ppc/platforms/4xx/bubinga.c
> @@ -89,7 +89,11 @@ bubinga_early_serial_map(void)
> * by 16.
> */
> uart_div = (mfdcr(DCRN_CPC0_UCR_BASE) & DCRN_CPC0_UCR_U0DIV);
> +#ifdef CONFIG_UBOOT
> + uart_clock = __res.bi_procfreq / uart_div;
> +#else
> uart_clock = __res.bi_pllouta_freq / uart_div;
> +#endif
Why not just rename this field and skip this ugly ifdefing?
--
Eugene
next prev parent reply other threads:[~2005-09-16 16:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 1:31 Address mapping PPC 405 P. Sadik
2005-08-26 3:10 ` Grant Likely
2005-08-26 22:47 ` Peter Ryser
2005-08-28 15:15 ` Jon Masters
2005-08-29 0:26 ` Grant Likely
2005-08-29 1:11 ` Jon Masters
2005-08-30 15:38 ` Matt Porter
2005-09-15 16:03 ` PPC4xx cleanup Stefan Roese
2005-09-15 16:25 ` Matt Porter
2005-09-15 19:03 ` Dan Malek
2005-09-19 14:08 ` Matt Porter
2005-09-16 11:06 ` [PATCH] ppc32: cleanup AMCC PPC4xx eval boards to better support U-Boot Stefan Roese
2005-09-16 16:27 ` Eugene Surovegin [this message]
2005-09-19 11:02 ` Stefan Roese
2005-09-19 13:59 ` Matt Porter
2005-09-19 15:06 ` Stefan Roese
2005-09-19 15:21 ` Matt Porter
2005-09-19 17:14 ` Eugene Surovegin
2005-11-22 17:34 ` [PATCH] ppc32: Add P3P440 (440GP) board support Stefan Roese
2005-09-19 11:20 ` [PATCH] ppc32: cleanup AMCC PPC44x eval boards to better support U-Boot Stefan Roese
2005-09-30 12:52 ` [PATCH] ppc32: cleanup AMCC PPC40x eval boards to " Stefan Roese
2005-10-28 15:58 ` [PATCH] ppc32: Remove internal PCI arbiter check on PPC40x Stefan Roese
2005-10-31 9:29 ` [PATCH] ppc32: Add missing initrd header on ppc440 Stefan Roese
2005-10-31 14:41 ` Matt Porter
2005-08-30 15:09 ` Address mapping PPC 405 Matt Porter
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=20050916162733.GA8019@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sr@denx.de \
/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).