From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: Fix memory attribute inconsistencies when using fixmap
Date: Wed, 22 Mar 2017 15:26:28 +0000 [thread overview]
Message-ID: <1490196388.2890.8.camel@linaro.org> (raw)
In-Reply-To: <CAKv+Gu8VoSLOUiNSXsrtQUr8TQdGBqiOmhsKS+N2dhToMusOUg@mail.gmail.com>
On Wed, 2017-03-22 at 12:13 +0000, Ard Biesheuvel wrote:
> On 22 March 2017 at 09:46, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:
> > On Tue, 2017-03-21 at 19:00 +0000, Ard Biesheuvel wrote:
> >
> > > Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > >
> > > UEFI boot and earlycon both still work for me, so
> > >
> > > Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
I forgot to say thanks?earlier, so thanks! :-)
> > > It looks like nommu should be unaffected, but it is worth giving it a
> > > spin as well
> >
> > I did build test a couple of nommu platforms. I'll try and work out how
> > to get Linux on the only nommu hardware I have (ARM's MPS2) but if that
> > kernel doesn't work before my applying my changes I'm not going to
> > debug, I've opened enough cans of worms for now.
> >
After much faffing around I got MPS2 booting a Linux kernel, and
somewhat to my surprise?it seems to boot fine, all the way up to
panicking because it didn't find an init. This was with $subject patch.
--
Tixy
next prev parent reply other threads:[~2017-03-22 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 17:30 [PATCH v2] arm: Fix memory attribute inconsistencies when using fixmap Jon Medhurst
2017-03-21 17:36 ` Jon Medhurst (Tixy)
2017-03-21 19:00 ` Ard Biesheuvel
2017-03-22 9:46 ` Jon Medhurst (Tixy)
2017-03-22 12:13 ` Ard Biesheuvel
2017-03-22 12:18 ` Russell King - ARM Linux
2017-03-22 15:26 ` Jon Medhurst (Tixy) [this message]
2017-03-24 20:17 ` afzal mohammed
2017-03-27 7:29 ` Ard Biesheuvel
2017-03-27 8:53 ` Jon Medhurst (Tixy)
2017-04-03 17:18 ` Ard Biesheuvel
2017-04-03 20:00 ` Russell King - ARM Linux
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=1490196388.2890.8.camel@linaro.org \
--to=tixy@linaro.org \
--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 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.