From: Bryan Huntsman <bryanh@codeaurora.org>
To: Jeremy Kerr <jeremy.kerr@canonical.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Eric Miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nico@fluxnic.net>,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC,PATCH 0/2] Allow late mdesc detection
Date: Wed, 14 Jul 2010 08:36:44 -0700 [thread overview]
Message-ID: <4C3DD98C.2000302@codeaurora.org> (raw)
In-Reply-To: <1279080712.15089.53.camel@pororo.lan>
> be useful without the DT. At present (and as far as I know), Grant and I
> are the only ones doing DT-specific infrastructure changes for ARM.
We did an evaluation of it a few months ago for MSM chips. IIRC, there
were a lot of work-arounds needed to accommodate platform data and
function pointers. The net result was not a decrease in board file size
or complexity. I'll try to find the tree we used and host it somewhere
for public review.
- Bryan
WARNING: multiple messages have this Message-ID (diff)
From: bryanh@codeaurora.org (Bryan Huntsman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC,PATCH 0/2] Allow late mdesc detection
Date: Wed, 14 Jul 2010 08:36:44 -0700 [thread overview]
Message-ID: <4C3DD98C.2000302@codeaurora.org> (raw)
In-Reply-To: <1279080712.15089.53.camel@pororo.lan>
> be useful without the DT. At present (and as far as I know), Grant and I
> are the only ones doing DT-specific infrastructure changes for ARM.
We did an evaluation of it a few months ago for MSM chips. IIRC, there
were a lot of work-arounds needed to accommodate platform data and
function pointers. The net result was not a decrease in board file size
or complexity. I'll try to find the tree we used and host it somewhere
for public review.
- Bryan
next prev parent reply other threads:[~2010-07-14 15:36 UTC|newest]
Thread overview: 20+ 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
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 [this message]
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=4C3DD98C.2000302@codeaurora.org \
--to=bryanh@codeaurora.org \
--cc=eric.y.miao@gmail.com \
--cc=jeremy.kerr@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
/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.