From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Commit 384a290283fde63ba8dc671fca5420111cdac19a seems to break 11MPCore boot
Date: Wed, 30 Jan 2013 18:03:31 +0000 [thread overview]
Message-ID: <20130130180331.GP23505@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1301301223290.6300@xanadu.home>
On Wed, Jan 30, 2013 at 12:30:06PM -0500, Nicolas Pitre wrote:
> That should probably be:
>
> u32 mask;
>
> for (i = 0; i < 32; i += 4) {
> mask = readl_relaxed(base + GIC_DIST_TARGET + i);
> mask |= (mask >> 16);
> mask |= (mask >> 8);
> if (mask)
> return mask;
> }
>
> I know that the spec says that the GIC should accept byte sized
> accesses, but that too is known not to work on all implementations.
Well, it really doesn't make that much difference... because from what
I can see the kernel is rather sodded up as it currently stands.
There was a time when the kernel ran on the ARM Realview EB. But it
doesn't today...
Why is it when I walk away from anything kernel related and then come
back to it, it's always sodded up and rather terminally broken?
next prev parent reply other threads:[~2013-01-30 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 15:23 Commit 384a290283fde63ba8dc671fca5420111cdac19a seems to break 11MPCore boot Punit Agrawal
2013-01-30 16:00 ` Nicolas Pitre
2013-01-30 16:05 ` Pawel Moll
2013-01-30 16:21 ` Russell King - ARM Linux
2013-01-30 16:45 ` Russell King - ARM Linux
2013-01-30 17:19 ` Russell King - ARM Linux
2013-01-30 17:30 ` Nicolas Pitre
2013-01-30 17:57 ` Will Deacon
2013-01-30 18:03 ` Russell King - ARM Linux [this message]
2013-01-30 18:16 ` Russell King - ARM Linux
2013-01-30 18:19 ` Russell King - ARM Linux
2013-01-30 20:30 ` Russell King - ARM Linux
2013-01-30 21:02 ` Nicolas Pitre
2013-01-30 16:04 ` Lorenzo Pieralisi
2013-01-30 16:40 ` Punit Agrawal
2013-01-30 16:56 ` Lorenzo Pieralisi
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=20130130180331.GP23505@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 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.