From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] irqchip: gic: Perform the gic_secondary_init() call via CPU notifier
Date: Thu, 31 Jan 2013 11:25:38 +0000	[thread overview]
Message-ID: <20130131112538.GW23505@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1301291907340.6300@xanadu.home>
On Tue, Jan 29, 2013 at 07:11:56PM -0500, Nicolas Pitre wrote:
> On Tue, 29 Jan 2013, Catalin Marinas wrote:
> > I would like to get them in as soon as possible (ideally 3.9) as AArch64
> > needs GIC support. I can base them on Rob's branch (already in -next)
> > and send them the same route (the arm-soc tree if Olof/Arnd are ok to
> > take them).
> 
> Well...  I'd prefer if my series was merged by RMK since this is mostly 
> core ARM code.  That is posing dependency issues.
> 
> I think I'll just ignore your change for now and we'll fix things up 
> during the v3.9-rc period.
Given that the ARM kernel seems to be rather broken at the moment, that's
not going to happen until the 32-bit kernel gets some loving attention to
make it work again.
Our primary responsibility is not to stuff the kernel with new features
as quickly as we possibly can.  It's to make sure that the kernel works,
and at the moment, it doesn't.  I'm not talking about ancient architectures.
I'm talking about platforms using ARMv6 and above - platforms with the GIC
which I'd be able to test this change on.
Realview EB (MPCore)
- Various failures yesterday but now works in my tree. Fixes queued for
  the next -rc.  (But the hardware randomly locks up during kernel boot,
  normally around the time when the CLCD is enabled, so this can't really
  be used for testing.)
OMAP4430SDP (Cortex A9)
- Fails to boot even with proper uImage addresses (no idea yet).  No
  kernel output.
OMAP3430LDP (Cortex A8 iirc)
- Ditto.  No kernel output.
I haven't tried Versatile Express yet as it has the TC2 tile on, and I
don't yet a boot loader on it which is capable of TFTP (which makes it
rather useless to me - I've been saying this for a time now but this is
probably the first time publically.)  I'm thinking about putting the
CA9x4 tile back on because that's a lot more functionally useful to me
than TC2.
next prev parent reply	other threads:[~2013-01-31 11:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 16:18 [PATCH v2 0/4] Preparatory GIC patches for arm64 support Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 1/4] arm: Move the set_handle_irq and handle_arch_irq declarations to asm/irq.h Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 2/4] arm: Move chained_irq_(enter|exit) to a generic file Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 3/4] irqchip: gic: Call handle_bad_irq() directly Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 4/4] irqchip: gic: Perform the gic_secondary_init() call via CPU notifier Catalin Marinas
2013-01-29 22:35   ` Nicolas Pitre
2013-01-29 23:12     ` Catalin Marinas
2013-01-30  0:11       ` Nicolas Pitre
2013-01-31 11:25         ` Russell King - ARM Linux [this message]
2013-01-31 11:49           ` Catalin Marinas
2013-01-31 17:32           ` Nicolas Pitre
2013-01-31 17:55             ` Russell King - ARM Linux
2013-01-31 20:31               ` Nicolas Pitre
2013-02-01 14:38                 ` Jon Medhurst (Tixy)
2013-02-01 17:39                   ` Nicolas Pitre
2013-01-30  0:31   ` Dinh Nguyen
2013-01-31 10:30 ` [PATCH v2 0/4] Preparatory GIC patches for arm64 support Catalin Marinas
2013-01-31 11:47   ` Russell King - ARM Linux
2013-01-31 12:32     ` Catalin Marinas
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=20130131112538.GW23505@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).