From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: Unifying cape overlays into boot .dtb for BeagleBoard.org boards Date: Tue, 17 Jun 2014 18:05:31 +0100 Message-ID: <20140617170531.GF3705@n2100.arm.linux.org.uk> References: <20140617090931.GB3705@n2100.arm.linux.org.uk> <20140617125831.GI4173@beef> <20140617131522.GD3705@n2100.arm.linux.org.uk> <20140617160119.GE3705@n2100.arm.linux.org.uk> <317D412E-B455-4B9D-95B3-F010C68744A3@antoniou-consulting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <317D412E-B455-4B9D-95B3-F010C68744A3@antoniou-consulting.com> Sender: linux-omap-owner@vger.kernel.org To: Pantelis Antoniou Cc: Matt Porter , Jason Kridner , beagleboard@googlegroups.com, Robert Nelson , devicetree@vger.kernel.org, OMAP List , ARM Kernel List , Grant Likely List-Id: devicetree@vger.kernel.org On Tue, Jun 17, 2014 at 07:59:21PM +0300, Pantelis Antoniou wrote: > That case might already work on FPGA people's trees. I know Altera for sure > uses overlays, and some xilinx guys popped up on past discussions. > Their vendor trees probably use an older revision of the patches. > > BTW, there is nothing special about DRM/v4l2 that can't be handled by > a generic DT mechanism. What makes this such a big problem? Really? DRM is not hotpluggable in any shape or form, and David Airlie has indicated that he does strongly opposes moving it in that direction. DRM follows the "card" model, where, at probe time, the hardware is known and never changes until the "card" is torn down. No new connectors can be added once the "card" is initialised, and no connectors can be removed. Any changes must be done by tearing down the entire card and reconstructing it (if reconstructing it with a reduced set of hardware is appropriate.) -- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it.