From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] WARNING: Caches not enabled on openrd based board
Date: Fri, 17 Aug 2012 17:24:56 +0200 [thread overview]
Message-ID: <20120817172456.758c2fbc@amdc308.digital.local> (raw)
In-Reply-To: <CANNiwJJ9P1Y1Qb0ybhg8Gviumd+EwTDmuJmy4T307ghEPbqmkg@mail.gmail.com>
On Fri, 17 Aug 2012 12:16:56 +0100
Alex Zeffertt <azeffertt@cambridgesys.com> wrote:
> Hi U-Booters,
>
> I get the following warning when I boot our openrd based board:
>
> > U-Boot 2012.07 (Aug 17 2012 - 10:45:29)
> > OpenRD-Base
> >
> > SoC: Kirkwood 88F6281_A1
> > DRAM: 128 MiB
> > WARNING: Caches not enabled
> > NAND: 512 MiB
>
> I am running the latest code from git with a small number of changes
> to make it work with our hardware.
> (In particular we have had to rewrite
> board/Marvell/openrd/kwbimage.cfg.)
>
> My question is: does the warning about caches affect only U-Boot (in
> which case I don't mind) or will it also affect Linux?
As fair as I know, it will only affect u-boot. If I remember correctly,
caches are disabled (and fulshed) just before passing execution to
linux.
Those caches are disabled, since some time ago it turns out, that many
drivers had problems with unaligned buffers allocation.
>
> TIA,
>
> Alex
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
--
Best regards,
Lukasz Majewski
Samsung Poland R&D Center | Linux Platform Group
next prev parent reply other threads:[~2012-08-17 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 11:16 [U-Boot] WARNING: Caches not enabled on openrd based board Alex Zeffertt
2012-08-17 15:24 ` Lukasz Majewski [this message]
2012-08-17 17:04 ` Alex Zeffertt
2012-08-18 10:03 ` Stefan Herbrechtsmeier
2012-08-21 7:27 ` Prafulla Wadaskar
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=20120817172456.758c2fbc@amdc308.digital.local \
--to=l.majewski@samsung.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