From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guenter Roeck Subject: Re: [PATCH 0/3 - V2] Introducing Device Tree Overlays Date: Wed, 6 Nov 2013 11:30:41 -0800 Message-ID: <20131106193041.GA26796@roeck-us.net> References: <1383676898-29819-1-git-send-email-panto@antoniou-consulting.com> <20131106190152.GA8662@breakpoint.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20131106190152.GA8662@breakpoint.cc> Sender: linux-kernel-owner@vger.kernel.org To: Sebastian Andrzej Siewior Cc: Pantelis Antoniou , Grant Likely , Rob Herring , Stephen Warren , Matt Porter , Koen Kooi , Alison Chaiken , Dinh Nguyen , Jan Lubbe , Alexander Sverdlin , Michael Stickel , Dirk Behme , Alan Tull , Sascha Hauer , Michael Bohan , Ionut Nicu , Michal Simek , Matt Ranostay , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org On Wed, Nov 06, 2013 at 08:01:52PM +0100, Sebastian Andrzej Siewior wrote: > On 05.11.13, Pantelis Antoniou wrote: > > The following patchset introduces Device Tree overlays, a method > > of dynamically altering the kernel's live Device Tree, along with > > a generic interface to use it in a board agnostic manner. > > In case this has been discussed and I missed it: Why are we doing this? > Isn't it possible to d o the overlay thingy in u-boot and pass a > complete device tree to the kernel? > Are you trying to do something like hotplug-PCI where the PCI card can > be replaced at runtime? > At least that is our use case. u-boot doesn't know which cards are going to be inserted at runtime. Even PCIe hotplug itself is insufficient, as the PCIe configuration differs per card, and the cards support a variety of i2c devices as well as other card specific devices such LEDs and multi-function FPGAs. Guenter