Thread (8 messages) 8 messages, 5 authors, 2012-11-05

Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2

From: Rob Herring <hidden>
Date: 2012-11-05 15:56:34
Also in: linux-omap, lkml

On 11/05/2012 08:34 AM, Grant Likely wrote:
On Mon, Nov 5, 2012 at 1:25 PM, Pantelis Antoniou
[off-list ref] wrote:
quoted
On Nov 5, 2012, at 1:22 AM, Grant Likely wrote:
quoted
On Fri, Nov 2, 2012 at 8:43 AM, Pantelis Antoniou
[off-list ref] wrote:
quoted
Assuming that we do work on a DT object format, and that the runtime resolution mechanism is approved,
then I agree that this part of the capebus patches can be dropped and the functionality assumed by generic
DT core.

The question is that this will take time, with no guarantees that this would be acceptable from
the device tree maintainers. So I am putting them in the CC list, to see what they think about it.
This is actually exactly the direction I want to go with DT, which the
ability to load supplemental DT data blobs from either a kernel module
or userspace using the firmware loading infrastructure.

g.
Hi Grant,

That's pretty much our use case.

Regards
Good. I'm about 80% though putting together a project plan of what is
required to implement this. I'll post it for RFC shortly. I would
appreciate feedback and help on flushing out the design.
The FPGA folks are also interested in dynamic DT configuration. There's
been some discussion and postings on the DT list in the last few months
you may have missed. It's maybe not completely the same use case, but
there is some overlap here.

Rob
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help