public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] irqchip: gic/realview: support more RealView DCC variants
Date: Thu, 18 Feb 2016 15:40:34 +0100	[thread overview]
Message-ID: <5028476.WAQS3ylXOd@wuerfel> (raw)
In-Reply-To: <56C5D304.5010708@arm.com>

On Thursday 18 February 2016 14:19:48 Marc Zyngier wrote:
> On 18/02/16 13:46, Linus Walleij wrote:
> > In the add-on file for the GIC dealing with the RealView family
> > we currently only handle the PB11MPCore, let's extend this to
> > manage the RealView EB ARM11MPCore as well. The Revision B of the
> > ARM11MPCore core tile is a bit special and needs special handling
> > as it moves a system control register around at random.
> 
> Ah, 11MPCore RevB. That thing. Tried to locate one in the magic
> cupboard, and failed. Oh well...

What surprised me though is that it's enabled by default:

$ grep REVB arch/arm/configs/realview*
arch/arm/configs/realview_defconfig:CONFIG_REALVIEW_EB_ARM11MP_REVB=y
arch/arm/configs/realview-smp_defconfig:CONFIG_REALVIEW_EB_ARM11MP_REVB=y

With that option set, the defconfig kernel should not be able
to boot on RevC machines. Do you have a RevC machine that works
with the defconfig?

	Arnd

  reply	other threads:[~2016-02-18 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 13:46 [PATCH 1/3] irqchip: gic/realview: support more RealView DCC variants Linus Walleij
2016-02-18 14:16 ` Arnd Bergmann
2016-02-18 14:19 ` Marc Zyngier
2016-02-18 14:40   ` Arnd Bergmann [this message]
2016-02-18 14:47     ` Marc Zyngier
2016-02-18 18:30     ` Linus Walleij
2016-02-19 11:14       ` Arnd Bergmann
2016-02-22  2:54 ` Rob Herring

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=5028476.WAQS3ylXOd@wuerfel \
    --to=arnd@arndb.de \
    --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