Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759590Ab2EDUeG (ORCPT ); Fri, 4 May 2012 16:34:06 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:48237 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754334Ab2EDUeD (ORCPT ); Fri, 4 May 2012 16:34:03 -0400 To: Arnd Bergmann cc: linux-arm-kernel@lists.infradead.org, Lee Jones , Mark Brown , Samuel Ortiz , Arnd Bergmann , Olof Johansson , Stephen Warren , Igor Grinberg , linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Walleij From: Wolfgang Denk Subject: Re: Handling of modular boards MIME-Version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 8bit In-reply-to: <201205041934.08830.arnd@arndb.de> References: <20120504185850.GO14230@opensource.wolfsonmicro.com> <201205041934.08830.arnd@arndb.de> Comments: In-reply-to Arnd Bergmann message dated "Fri, 04 May 2012 19:34:08 -0000." Date: Fri, 04 May 2012 22:33:57 +0200 Message-Id: <20120504203357.6B79B206451@gemini.denx.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1630 Lines: 37 Dear Arnd, In message <201205041934.08830.arnd@arndb.de> you wrote: > > One idea that I've heard before is to put device tree fragments into the > kernel and dynamically add them to the device tree that was passed by the > boot loader whenever we detect the presence of a specific device. > This obviously means it works only for boards using DT for booting, but > it allows us to use some infrastructure that we already have. > > Another idea was to put all the possible extensions into the device tree > for a given board and disable them by default, putting it into the > responsibility of the boot loader to enable the one that is actually > being used. This has serious scalibility problems when there are many > possible extensions and also relies more on the boot loader than I would > like. On the other hand, some of the issues we're trying to solve here for the kernel are also present in the boot loader, so this needs to do this anyway - whether by inserting new or modifying (enabling or disabling) existing properties in the DT is not really relevant here. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Our business is run on trust. We trust you will pay in advance. -- 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/