From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC,PATCH 0/2] Allow late mdesc detection
Date: Tue, 13 Jul 2010 08:28:48 +0100 [thread overview]
Message-ID: <20100713072848.GC19839@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTikXejaVsFsudO3ABKzR80V6yCBHm7c6y32hurdt@mail.gmail.com>
On Tue, Jul 13, 2010 at 01:44:59PM +0800, Eric Miao wrote:
> With the introduction of 'struct machine_class', I guess this is especially
> true for 1 SoC for one DT machine ID :-)
>
> Finally, if we can decide the 'struct machine_class' by something else,
> then we can merge all DT machine IDs into one or completely ignore it.
As far as I can see, DT isn't getting anywhere - certainly my request
to see it on a real platform rather than the ARM Ltd hardware seems to
have been "forgotten" about.
As it's taking soo long (it's getting to be a couple of years) to come
up with a DT implementation for a real machine, I can only think that
there must be some massive problem(s) with DT which makes it completely
unsuitable for use on ARM.
next prev parent reply other threads:[~2010-07-13 7:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 3:03 [RFC,PATCH 0/2] Allow late mdesc detection Jeremy Kerr
2010-07-12 3:03 ` [RFC,PATCH 1/2] arm: don't check MMU status in every addruart macro Jeremy Kerr
2010-07-12 13:32 ` [RFC, PATCH " Nicolas Pitre
2010-07-13 1:39 ` Jeremy Kerr
2010-07-12 3:03 ` [RFC,PATCH 2/2] arm: use addruart macro to establish debug mappings Jeremy Kerr
2010-07-12 13:42 ` [RFC, PATCH " Nicolas Pitre
2010-07-12 13:52 ` [RFC,PATCH " Russell King - ARM Linux
2010-07-13 1:42 ` Jeremy Kerr
2010-07-12 3:39 ` [RFC,PATCH 0/2] Allow late mdesc detection Nicolas Pitre
2010-07-12 8:05 ` Jeremy Kerr
2010-07-12 8:39 ` Eric Miao
2010-07-12 13:11 ` Nicolas Pitre
2010-07-13 5:44 ` Eric Miao
2010-07-13 7:28 ` Russell King - ARM Linux [this message]
2010-07-13 9:02 ` Jeremy Kerr
2010-07-13 9:33 ` Russell King - ARM Linux
2010-07-14 3:25 ` Nicolas Pitre
2010-07-14 4:11 ` Jeremy Kerr
2010-07-14 15:36 ` Bryan Huntsman
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=20100713072848.GC19839@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).