From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: [RFC] Device Tree Overlays Proposal (Was Re: capebus moving omap_devices to mach-omap2) Date: Thu, 8 Nov 2012 08:09:19 -0600 Message-ID: <509BBD0F.3030702@freescale.com> References: <6AE080B68D46FC4BA2D2769E68D765B708174B7D@039-SN2MPN1-023.039d.mgd.msft.net> <509AE247.3000404@gmail.com> <356155A1-776B-4AA5-A912-14CE7D9AE42C@dominion.thruhere.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <356155A1-776B-4AA5-A912-14CE7D9AE42C@dominion.thruhere.net> Sender: linux-kernel-owner@vger.kernel.org To: Koen Kooi Cc: Ryan Mallon , Grant Likely , Pantelis Antoniou , Rob Herring , Deepak Saxena , Benjamin Herrenschmidt , Wood Scott-B07421 , Tony Lindgren , Kevin Hilman , Matt Porter , linux-kernel , Felipe Balbi , Russ Dill , "linux-omap@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" List-Id: linux-omap@vger.kernel.org Koen Kooi wrote: > And as Pantelis mentioned before, I really don't want my users to change the bootloader whenever they add a new LED. Well, U-Boot does allow you to manipulate the device tree from the command-line, but I understand that this feature doesn't work that well. -- Timur Tabi Linux kernel developer at Freescale