From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: Activating dcache breaks 'usb start' and 'tftpboot' on jadecpu
Date: Fri, 03 Dec 2010 16:09:13 +0100 [thread overview]
Message-ID: <4CF90819.7040904@arcor.de> (raw)
In-Reply-To: <20101203144745.21D23CD138A@gemini.denx.de>
Hello Wolfgang
Am 03.12.2010 15:47, schrieb Wolfgang Denk:
>> Has anyone an explanation for this behavior? Is anyone out there having
>> dcache running on an ARM926 and working usb/tftpboot?
>
> Many drivers have not been written to work with enabled caches.
What is the reason that special handling is needed when dcache is
enabled? If a driver doesn't use any DMA there should be no need as the
dcache is only enabled for the RAM and not for any memory mapped IO if I
understand the code in arch/arm/lib/cache-cp15.c right.
> As far as USB is concerned, you might be lucky that your system usies
> a EHCI controller, so setting CONFIG_EHCI_DCACHE should help.
No, only OHCI.
> As for the network driver, you will probably have to figure out
> yourself how to fix that.
As the memory mapped network controller (SMSC9221) is not cached it
shouldn't be a problem or do I miss something here?
> Patches welcome.
If someone can give me a little push into the right direction I will try
but currently I have no idea what to do besides activating the cache
right before the default "bootm" booting.
Thanks a lot
Matthias
next prev parent reply other threads:[~2010-12-03 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 14:27 [U-Boot] arm: Activating dcache breaks 'usb start' and 'tftpboot' on jadecpu Matthias Weißer
2010-12-03 14:47 ` Wolfgang Denk
2010-12-03 15:09 ` Matthias Weißer [this message]
2010-12-03 15:33 ` Wolfgang Denk
2010-12-03 16:34 ` Albert ARIBAUD
2010-12-03 16:48 ` Matthias Weißer
2010-12-03 16:43 ` Matthias Weißer
2010-12-03 16:55 ` Wolfgang Denk
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=4CF90819.7040904@arcor.de \
--to=weisserm@arcor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.