From: Mark Rutland <mark.rutland@arm.com>
To: Guenter Roeck <linux@roeck-us.net>,
Michael Bohan <mbohan@codeaurora.org>
Cc: David Daney <ddaney@caviumnetworks.com>,
David Gibson <david@gibson.dropbear.id.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"ralf@linux-mips.org" <ralf@linux-mips.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"david.daney@cavium.com" <david.daney@cavium.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [PATCH] of/lib: Export fdt routines to modules
Date: Fri, 18 Oct 2013 19:38:04 +0100 [thread overview]
Message-ID: <20131018183804.GA8546@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <52608457.5040609@roeck-us.net>
Hi all,
Guenter, thanks for adding devicetree to Cc.
On Fri, Oct 18, 2013 at 01:44:07AM +0100, Guenter Roeck wrote:
> On 10/17/2013 04:51 PM, Michael Bohan wrote:
> > On Wed, Oct 16, 2013 at 09:54:27PM -0700, Guenter Roeck wrote:
> >> On 10/16/2013 05:27 PM, Michael Bohan wrote:
> >>> My motivation is actually to use the fdt format as a firmware.
> >>> I have a requirement to express driver metadata that's loadable
> >> >from the filesystem. This data is not reasonable to place in the
> >>> system Device Tree, since it's application specific and does not
> >>> actually describe hardware. The fact that the format chosen is
> >>> 'flattened device tree' is merely just a coincidence.
Michael, could you elaborate on using the fdt format "as a firmware" and
what driver metadata you need to be loadable from the filesystem?
How are you intending to pass the DT to the kernel from userspace?
Given that you mention this is application-specific configuration, why
is using sysfs attributes or some other sort of filesystem interaction
not appropriate?
Thanks,
Mark.
next prev parent reply other threads:[~2013-10-18 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1381966065-16854-1-git-send-email-mbohan@codeaurora.org>
[not found] ` <525F2397.40203@caviumnetworks.com>
[not found] ` <20131017002731.GA22830@codeaurora.org>
[not found] ` <525F6D83.1050808@roeck-us.net>
[not found] ` <20131017235132.GA6241@codeaurora.org>
2013-10-18 0:44 ` [PATCH] of/lib: Export fdt routines to modules 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
[not found] ` <52616228.80002-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
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-19 1:49 ` Michael Bohan
2013-10-19 3:41 ` Guenter Roeck
2013-10-18 18:38 ` Mark Rutland [this message]
[not found] ` <20131018183804.GA8546-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
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=20131018183804.GA8546@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--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=mbohan@codeaurora.org \
--cc=panto@antoniou-consulting.com \
--cc=ralf@linux-mips.org \
--cc=rob.herring@calxeda.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 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).