linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: vexpress: Remove non-DT code
Date: Thu, 18 Sep 2014 08:57:58 +0100	[thread overview]
Message-ID: <20140918075758.GA12361@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.11.1409172059050.8647@knanqh.ubzr>

On Wed, Sep 17, 2014 at 09:04:54PM -0400, Nicolas Pitre wrote:
> On Wed, 17 Sep 2014, Russell King - ARM Linux wrote:
> 
> > As for TC2, I just don't bother with that.  It's really not worth the
> > hastle.  I asked for help with that and got almost nothing.  Yes, there's
> > Nicolas' uboot, which solves some problems, but getting the kernel to
> > boot on TC2 turned out to be a dead loss - and no help with it was
> > forthcoming.
> 
> TC2 is my main development board at the moment and it boots mainline 
> perfectly.  If you want I can provide you with a tarball of everything 
> you need to boot it, including my setup script and compiled kernel, to 
> get you started.

Well, right now I have a slightly different view, because of the work on
the FIQ stuff.

We currently have the situation where the GIC on CT9x4 appears to be
different from other GICs, in that group 1 interrupts are never
delivered.  As the GIC is indistinguishable from working parts, this
currently squarely puts the Daniel's KGDB FIQ work, and work to use
FIQ for dumping backtraces in the case of a spinlock lockup beyond the
reach of the kernel right now, and nothing more than a local hack.

So, until we get to the bottom of this, I need Versatile Express support
to stay as-is, so there's no extraneous variables in the platform.  That
means right now I need the legacy stuff to stay as switching to DT will
add a huge variable into what's going on.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-09-18  7:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 14:33 [PATCH 1/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2014-09-10 14:33 ` [PATCH 2/2] ARM: vexpress: Remove non-DT code Pawel Moll
2014-09-10 14:58   ` Russell King - ARM Linux
2014-09-10 15:40     ` Pawel Moll
2014-09-17 15:27       ` Russell King - ARM Linux
2014-09-17 16:11         ` Pawel Moll
2014-09-18  1:04         ` Nicolas Pitre
2014-09-18  7:57           ` Russell King - ARM Linux [this message]
2014-09-18  9:19             ` Pawel Moll
2014-09-18 17:17             ` Nicolas Pitre
2014-09-10 17:45   ` Mike Turquette
2014-09-16 23:30   ` Lee Jones
2014-09-17 14:59     ` Pawel Moll
2014-09-17 15:42       ` Lee Jones
2014-09-17 15:46         ` Pawel Moll
2014-09-17 16:54           ` Lee Jones
2014-09-17 16:43   ` [PATCH v2] " Pawel Moll

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=20140918075758.GA12361@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).