From: Tabi Timur-B04825 <B04825@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] [v3] powerpc/85xx: introduce and document CONFIG_SYS_CCSRBAR macros
Date: Fri, 5 Aug 2011 13:11:33 +0000 [thread overview]
Message-ID: <4E3BEC05.6000704@freescale.com> (raw)
In-Reply-To: <9180ADCE-F2F6-4ABC-BAE6-060CE06790E4@freescale.com>
Kumar Gala wrote:
> Why didn't we do in include/mpc85xx.h:
>
> #ifndef CONFIG_SYS_CCSRBAR_PHYS_LOW
> #define CONFIG_SYS_CCSRBAR_PHYS_LOW CONFIG_SYS_CCSRBAR
> #endif
>
> Thus removing that line from every board file?
That might make more sense, but that will break other boards where virtual
!= physical but CCSR is not relocated, which means another round of
testing. MAKEALL takes a long time to run.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-08-05 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 23:03 [U-Boot] [PATCH 1/2] [v3] powerpc/85xx: introduce and document CONFIG_SYS_CCSRBAR macros Timur Tabi
2011-08-04 23:03 ` [U-Boot] [PATCH 2/2] powerpc/85xx: relocate CCSR before creating the initial RAM area Timur Tabi
2011-08-05 13:01 ` [U-Boot] [PATCH 1/2] [v3] powerpc/85xx: introduce and document CONFIG_SYS_CCSRBAR macros Kumar Gala
2011-08-05 13:11 ` Tabi Timur-B04825 [this message]
2011-08-05 13:43 ` Kumar Gala
2011-08-05 13:49 ` Tabi Timur-B04825
2011-08-26 19:04 ` Kumar Gala
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=4E3BEC05.6000704@freescale.com \
--to=b04825@freescale.com \
--cc=u-boot@lists.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