From: Michael Bohan <mbohan@codeaurora.org>
To: Rob Herring <robherring2@gmail.com>
Cc: David Daney <ddaney@caviumnetworks.com>,
Pantelis Antoniou <panto@antoniou-consulting.com>,
Guenter Roeck <linux@roeck-us.net>,
David Gibson <david@gibson.dropbear.id.au>,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, ralf@linux-mips.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
david.daney@cavium.com, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] of/lib: Export fdt routines to modules
Date: Fri, 18 Oct 2013 18:49:19 -0700 [thread overview]
Message-ID: <20131019014919.GB30244@codeaurora.org> (raw)
In-Reply-To: <5261A609.1020605@gmail.com>
On Fri, Oct 18, 2013 at 04:20:09PM -0500, Rob Herring wrote:
> On 10/18/2013 02:32 PM, Michael Bohan wrote:
> > My preference is probably straight libfdt calls, but if others
> > think that unpacking is a better solution, I'm able to go that
> > route as well. My only concern there is that we provide a means
> > to detect invalid dtb image (ex. handle error codes) and also
> > free the device_node allocations once the device is released.
>
> I think we need to understand what you are putting in the DT first.
That's understandable. Please see my response to Mark.
> Given there are other desired uses like overlays which need to add the
> necessary loading and unflattening support, a common solution is likely
> more desirable.
But by convention, would overlays allow for 'application
specific' data, or are they expected to meet the more rigid
requirements of a real Device Tree?
Thanks,
Mike
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-10-19 1:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 23:27 [PATCH] of/lib: Export fdt routines to modules Michael Bohan
2013-10-16 23:39 ` David Daney
2013-10-16 23:39 ` David Daney
2013-10-17 0:27 ` Michael Bohan
2013-10-17 4:54 ` Guenter Roeck
2013-10-17 23:51 ` Michael Bohan
2013-10-18 0:44 ` Guenter Roeck
2013-10-18 2:54 ` Michael Bohan
2013-10-18 13:28 ` Pantelis Antoniou
2013-10-18 15:57 ` Rob Herring
2013-10-18 16:16 ` Guenter Roeck
2013-10-18 16:30 ` David Daney
2013-10-18 16:30 ` David Daney
[not found] ` <52616228.80002-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2013-10-18 19:32 ` Michael Bohan
2013-10-18 19:32 ` Michael Bohan
[not found] ` <20131018193229.GA30141-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-10-18 21:20 ` Rob Herring
2013-10-18 21:20 ` Rob Herring
2013-10-19 1:49 ` Michael Bohan [this message]
2013-10-19 3:41 ` Guenter Roeck
2013-10-18 18:38 ` Mark Rutland
[not found] ` <20131018183804.GA8546-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-10-19 1:41 ` Michael Bohan
2013-10-19 1:41 ` Michael Bohan
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=20131019014919.GB30244@codeaurora.org \
--to=mbohan@codeaurora.org \
--cc=david.daney@cavium.com \
--cc=david@gibson.dropbear.id.au \
--cc=ddaney@caviumnetworks.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=panto@antoniou-consulting.com \
--cc=ralf@linux-mips.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
/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.