From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] integratorap: disable dcache
Date: Fri, 15 Jul 2011 09:42:53 +0200 [thread overview]
Message-ID: <4E1FEF7D.5050007@denx.de> (raw)
In-Reply-To: <CACRpkdZeDMUWS-0WNHXT8M9wV0JhXGDNOtrg+khdhPKsAbi_qA@mail.gmail.com>
Hello Linus,
Linus Walleij wrote:
> On Thu, Jul 14, 2011 at 1:39 PM, Wolfgang Denk <wd@denx.de> wrote:
>
>> Sorry, but again I have to point out that I really dislike papering
>> over existing bugs. If the disable D-cache in bootm does not work,
>> _this_ should be analyzed and fixed instead of globally disabling he
>> data cache.
>
> No problem, I didn't label it as RFC since what it does is actually fix a
> regression.
>
> At one point U-boot was working on the Integrator and now
> it doesn't, it seems commit 880eff5cfb9df6f0855f4e48affd349ca64692e9
> "ARM: cp15: setup mmu and enable dcache" is causing it.
>
> Heiko, Alessandro, do you have any hints on how to go about flushing
> and disabling the D-cache in bootm for ARM920T? It doesn't seem to
> work on this ARM CPU chip in its current form...
Hmm.. trying bootm with actual u-boot on a davinci (arm926ejs) based
board, there I couldn;t use the Davinci-EMAC (if I disable the dcache
it works ...)
Seems above commit introduced problems for other arm architectures,
drivers, ...
Hmm... if we globally always enable the dcache, we have a lot of more
drivers to fix (I think) ...
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2011-07-15 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 23:04 [U-Boot] [PATCH 1/2] integratorap: disable dcache Linus Walleij
2011-07-14 11:39 ` Wolfgang Denk
2011-07-14 17:57 ` Linus Walleij
2011-07-15 7:42 ` Heiko Schocher [this message]
2011-07-15 8:54 ` Laurence Withers
2011-07-15 9:31 ` Stefan Roese
2011-07-15 9:36 ` Linus Walleij
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=4E1FEF7D.5050007@denx.de \
--to=hs@denx.de \
--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