From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.16-rc1 & default cachepolicy
Date: Fri, 20 Jun 2014 00:36:26 +0100 [thread overview]
Message-ID: <20140619233626.GI3705@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140619224004.GF558@drone.musicnaut.iki.fi>
On Fri, Jun 20, 2014 at 01:40:04AM +0300, Aaro Koskinen wrote:
> So I tried the below change. But now it hangs early, even before
> the earlyprintk is working. :-/
Thanks for trying. I notice you said "write-through", so can you
drop the PMD_SECT_BUFFERABLE flag and try again please?
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-19 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 20:36 v3.16-rc1 & default cachepolicy Aaro Koskinen
2014-06-19 20:58 ` Russell King - ARM Linux
2014-06-19 22:40 ` Aaro Koskinen
2014-06-19 23:36 ` Russell King - ARM Linux [this message]
2014-06-20 8:57 ` Aaro Koskinen
2014-06-20 10:26 ` [PATCH] ARM: arm925: ensure assembly sets up writethrough mapping Russell King
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=20140619233626.GI3705@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).