From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] [v4] powerpc/85xx: introduce and document CONFIG_SYS_CCSRBAR macros
Date: Fri, 5 Aug 2011 12:51:48 -0500 [thread overview]
Message-ID: <4E3C2DB4.60904@freescale.com> (raw)
In-Reply-To: <1312558578-21800-1-git-send-email-timur@freescale.com>
Timur Tabi wrote:
> Introduce the CONFIG_SYS_CCSRBAR_PHYS_HIGH and CONFIG_SYS_CCSRBAR_PHYS_LOW
> macros, which contain the high and low portions of CONFIG_SYS_CCSRBAR_PHYS.
> This is necessary for the assembly-language code that relocates CCSR, since
> the assembler does not understand 64-bit constants.
Sorry, there are only supposed to be two patches in the patchset. There is no
[PATCH 3/3].
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2011-08-05 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 15:36 [U-Boot] [PATCH 1/3] [v4] powerpc/85xx: introduce and document CONFIG_SYS_CCSRBAR macros Timur Tabi
2011-08-05 15:36 ` [U-Boot] [PATCH 2/3] powerpc/85xx: relocate CCSR before creating the initial RAM area Timur Tabi
2011-08-26 19:05 ` Kumar Gala
2011-08-05 17:51 ` Timur Tabi [this message]
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=4E3C2DB4.60904@freescale.com \
--to=timur@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