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
parent reply other threads:[~2010-07-14 15:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1279080712.15089.53.camel@pororo.lan>]
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 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).