From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 14/15] Introduce arch_phys_memset which works like memset but on physical memory
Date: Mon, 3 Dec 2012 08:59:51 -0500 [thread overview]
Message-ID: <50BCB057.3060809@ti.com> (raw)
In-Reply-To: <1354460119-23877-15-git-send-email-sjg@chromium.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/02/12 09:55, Simon Glass wrote:
> From: Gabe Black <gabeblack@chromium.org>
>
> The default implementation of this function is just memset, but
> other implementations will be needed when physical memory isn't
> accessible by U-Boot using normal addressing mechanisms.
>
> Signed-off-by: Gabe Black <gabeblack@chromium.org> Signed-off-by:
> Che-Liang Chiou <clchiou@chromium.org> Signed-off-by: Simon Glass
> <sjg@chromium.org>
We've supported PowerPC platforms with 36bit memory ranges for ages.
Part of that however I believe is just not touching that high memory
range. So why do we need to touch the range here, rather than just
configuring the memory controller and booting Linux? Is this for some
hardware tester for example?
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQvLBWAAoJENk4IS6UOR1WS3oP/3OslD0jJzixbYNn35N+4KjY
dgnkNuLYwiXPhsw9sRttNihf7C2XLfPtbJfQo97hAVSgULLgBjjRN4HtoB9Yx3M1
hMtPcWzt/JxOOzgKwUBF1RdFwQ8ENmD0AYQ3F6D3uNq/3Tez9/VkrrXpbMnNvNyh
cw1fKT0aFDJgTdoK6KWRvXd1Z/cQk0+aWDFXhi1Y1yBag80PKXoiEATrd3hg1Tig
MVFu3QFxjGcYWkZiFtEpn4fpFLzhZVbmxzOzq/JTT33fH60ZJewCkUTVw3zfqBHE
bGyGiNhzZa4Se7cgtL4mkWEGyAmapfMwowM7SPqw3gew5G8lFZdpIKTe+4ECGEdH
dcHaXb28KghE8XUdcA02cWd0COhyFpdsJxuzqzKg3J8S/b4DMLMFcJRalBfTMcm3
T9fSDxa5DwiEoJd0/HTF5ZBR4QQoAp9EOrNU+y2zjF9U7y5USA1smoXSBKQGtZTL
sCB3FFfrGoDHiVks4lhEDqGT+eFPK2cYZzi8RCG3sP8MhfNzaw7ZjUfwi2zjdu/D
scIAh8RexrAvuIG5svqTun7YppRFbTINSIB2Z3WVievJGCUa72ke5eC9cSAaW5Uv
MNoURhgp4lqXLNPiYyKMtJEgyQQrSQVT4Ty0MfxSEWwZVKrU6AQ2OGe/xCHiejSw
0QqmDjrlA/4ntaimuw14
=ahxh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-03 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 14:55 [U-Boot] [PATCH v2 07/15] x86: Import MSR/MTRR code from Linux Simon Glass
2012-12-02 14:55 ` [U-Boot] [PATCH v2 14/15] Introduce arch_phys_memset which works like memset but on physical memory Simon Glass
2012-12-02 19:33 ` Wolfgang Denk
2012-12-02 21:16 ` Simon Glass
2012-12-02 22:26 ` Wolfgang Denk
2012-12-03 13:59 ` Tom Rini [this message]
2012-12-03 17:58 ` Simon Glass
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=50BCB057.3060809@ti.com \
--to=trini@ti.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