From: Lucas Stach <dev@lynxeye.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org,
Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Subject: Re: [PATCH] ARM: invalidate data caches during early init
Date: Mon, 20 May 2013 17:21:37 +0200 [thread overview]
Message-ID: <1369063297.1918.2.camel@antimon> (raw)
In-Reply-To: <20130518091137.GV32299@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 828 bytes --]
Am Samstag, den 18.05.2013, 11:11 +0200 schrieb Sascha Hauer:
> On Fri, May 17, 2013 at 09:06:45PM +0200, Lucas Stach wrote:
> > Am Freitag, den 17.05.2013, 10:35 +0200 schrieb Sascha Hauer:
> > > Some SoCs come up with invalid entries in the data cache. This can
> > > lead to memory corruption when we enable them later, so invalidate
> > > the caches early.
> > >
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > CC: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> >
> > Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
> > Tested-by: Lucas Stach <l.stach@pengutronix.de>
>
> Cool. Does that mean the MMU now works on Tegra?
Yep. I've tested both MMU and EARLY_MMU with this patch applied
(together with some of my WIP stuff) and it now works without any
problems.
Regards,
Lucas
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5715 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-05-20 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 8:35 Sascha Hauer
2013-05-17 19:06 ` Lucas Stach
2013-05-18 9:11 ` Sascha Hauer
2013-05-20 15:21 ` Lucas Stach [this message]
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=1369063297.1918.2.camel@antimon \
--to=dev@lynxeye.de \
--cc=barebox@lists.infradead.org \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=s.hauer@pengutronix.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