From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: -next fails to boot as of today on S3C6410
Date: Thu, 24 Nov 2011 18:02:28 +0000 [thread overview]
Message-ID: <20111124180228.GA32119@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1111241254310.17904@xanadu.home>
On Thu, Nov 24, 2011 at 12:59:38PM -0500, Nicolas Pitre wrote:
> No. The s3c64xx code is wrong. It relies on a freshly installed
> mapping that has not been flushed to RAM yet. So when it works for you,
> That's due to pure luck, most probably because the page table is not
> cached when the mapping is created and the cache is not allocated on
> write.
Ah, right - I was assuming that the existing code was OK (given that
it's been in use for years). What should it be doing to trigger the
flush?
next prev parent reply other threads:[~2011-11-24 18:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 19:27 -next fails to boot as of today on S3C6410 Mark Brown
2011-11-22 19:31 ` Russell King - ARM Linux
2011-11-22 19:39 ` Mark Brown
2011-11-22 22:21 ` Jamie Iles
2011-11-22 22:58 ` Mark Brown
2011-11-22 23:03 ` Jamie Iles
2011-11-22 23:34 ` Rob Herring
2011-11-23 12:05 ` Mark Brown
2011-11-23 12:28 ` Jamie Iles
2011-11-23 13:01 ` Mark Brown
2011-11-23 13:32 ` Jamie Iles
2011-11-23 13:50 ` Mark Brown
2011-11-23 14:33 ` Jamie Iles
2011-11-23 14:55 ` Mark Brown
2011-11-23 17:52 ` Rob Herring
2011-11-23 17:54 ` Mark Brown
2011-11-23 19:08 ` Nicolas Pitre
2011-11-24 0:32 ` Nicolas Pitre
2011-11-24 12:09 ` Mark Brown
2011-11-24 12:56 ` Mark Brown
2011-11-24 16:08 ` Mark Brown
2011-11-24 17:59 ` Nicolas Pitre
2011-11-24 18:02 ` Mark Brown [this message]
2011-11-24 18:22 ` Nicolas Pitre
2011-11-24 18:31 ` Mark Brown
2011-11-24 18:37 ` Nicolas Pitre
2011-11-24 18:40 ` Nicolas Pitre
2011-11-24 18:49 ` Mark Brown
2011-11-26 21:52 ` Russell King - ARM Linux
2011-11-27 0:28 ` Nicolas Pitre
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=20111124180228.GA32119@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).