Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932497Ab2KEOeY (ORCPT ); Mon, 5 Nov 2012 09:34:24 -0500 Received: from mail-pa0-f46.google.com ([209.85.220.46]:59470 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932439Ab2KEOeW (ORCPT ); Mon, 5 Nov 2012 09:34:22 -0500 MIME-Version: 1.0 In-Reply-To: References: <1351783082-11411-1-git-send-email-panto@antoniou-consulting.com> <20121031175219.GH12739@atomide.com> <20121031180935.GL12739@atomide.com> <50918223.6080003@ti.com> <8AD2F7AF-8315-442B-A394-1A38DAB29F52@antoniou-consulting.com> <20121031212639.GQ12739@atomide.com> <8B058B00-6C21-4410-A24B-75651D49F6EC@antoniou-consulting.com> <20121031221402.GA29490@arwen.pp.htv.fi> <50924DA3.1060901@ti.com> <50925C49.7060004@ti.com> <50938108.5040507@ti.com> <40797D3D-D62C-4E15-B0DF-75636C1637EE@antoniou-consulting.com> From: Grant Likely Date: Mon, 5 Nov 2012 14:34:01 +0000 X-Google-Sender-Auth: nTWpEVdOuZ0iD2HRIxBWPanM1CE Message-ID: Subject: Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2 To: Pantelis Antoniou Cc: "Cousson, Benoit" , Koen Kooi , Felipe Balbi , Tony Lindgren , linux-kernel , Matt Porter , Russ Dill , linux-omap@vger.kernel.org, Kevin Hilman , Paul Walmsley , devicetree-discuss@lists.ozlabs.org, Rob Herring Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1401 Lines: 36 On Mon, Nov 5, 2012 at 1:25 PM, Pantelis Antoniou wrote: > > On Nov 5, 2012, at 1:22 AM, Grant Likely wrote: > >> On Fri, Nov 2, 2012 at 8:43 AM, Pantelis Antoniou >> wrote: >>> 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. g. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/