From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pxa: Disable dcache on palmld, palmtc, zipitz2
Date: Wed, 31 Oct 2012 07:44:54 -0700 [thread overview]
Message-ID: <50913966.2010808@ti.com> (raw)
In-Reply-To: <201210311255.51276.marex@denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/31/12 04:55, Marek Vasut wrote:
> Dear Simon Glass,
>
>> These platforms don't include dcache support. Define
>> CONFIG_SYS_DCACHE_OFF so that functions don't try to call
>> non-existent routines like flush_dcache_range().
>>
>> Signed-off-by: Simon Glass <sjg@chromium.org>
>
> Is that needed? Why not fix PXA by defining stub cache routines ?
Adding stubs sounds more like a work-around than disabling support
that we won't have to me.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQkTllAAoJENk4IS6UOR1WLr4P/A+W1cl1MV2aBrLH0VMPCjzn
M3oOHvn2TQDbIZawIVf1AXbAv6BVfdLWg4XUQFsfnU/sFS3gGZccK4U4aCVqwoXv
ewUD6L7UgT9GeKCSvACDIwx0T3xntSO5B6+fzESyDzE2I04ZjnUyP5cKkXZWNJdH
XTB0F5BP6EgPwGtfvl/5gjWajuDLyPnuyd+kLY8LOsBc5g6ELORkjQGMeVzs1Qe9
rFtQfw/g/ie3Qq7O7UDmaliJq7iLiZL7aSam/+20so0JzvTYTspT9lk6Gt2yRJRU
iLA3J53BOsU4JnZ28PwfHycQEKxFhYWLUAyhO6G8wMjod7NEcwC138ywvoOFX1xg
A/wWiorxt94nioiZmRAVOwQKNiIiPLCJg4T2j5BzhhUvK/xT3F2lhcI8fF9HpVt4
dKzVRpO3TvtYXVLajpRVuoVVUkiInwo68NEHv6cZZDsKFKOWKG6zmEotVR9xAf1y
3NHz+d8j78Ach5k4O7bJXDZKIO+s3ak3Oa6uHUmz0oPwPnb9PsLNd3B/Ds5uMLsB
BsHREAk7f+K6cRH4vWZOfJ2vuuLMViR5+lIsPAUKMi9uPVM3qG/MFcrkr0pqAML7
8a6kn/9lAmPquQCm3t7tLgJNhZkMuMokFLGFe6oQDGSNdxeaOSPmxli2W464vhsh
T0l9Gi6Mb3yAbJuMYnJM
=AJDZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-31 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 23:38 [U-Boot] [PATCH] pxa: Disable dcache on palmld, palmtc, zipitz2 Simon Glass
2012-10-31 11:55 ` Marek Vasut
2012-10-31 14:44 ` Tom Rini [this message]
2012-10-31 16:41 ` Marek Vasut
2012-10-31 16:52 ` Tom Warren
2012-11-05 20:47 ` Simon Glass
2012-11-05 22:59 ` Marek Vasut
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=50913966.2010808@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