linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wd@denx.de (Wolfgang Denk)
To: linux-arm-kernel@lists.infradead.org
Subject: Handling of modular boards
Date: Fri, 04 May 2012 22:33:57 +0200	[thread overview]
Message-ID: <20120504203357.6B79B206451@gemini.denx.de> (raw)
In-Reply-To: <201205041934.08830.arnd@arndb.de>

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 at denx.de
Our business is run on trust.  We trust you will pay in advance.

  parent reply	other threads:[~2012-05-04 20:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 18:58 Handling of modular boards Mark Brown
2012-05-04 19:34 ` Arnd Bergmann
2012-05-04 20:07   ` Mark Brown
2012-05-04 20:33   ` Wolfgang Denk [this message]
2012-05-04 20:39     ` Arnd Bergmann
2012-05-04 20:54       ` Wolfgang Denk
2012-05-04 21:03         ` Arnd Bergmann
2012-05-04 21:09           ` Stephen Warren
2012-05-04 21:52             ` Mark Brown
2012-05-04 22:09     ` Mark Brown
2012-05-10 10:41       ` Ben Dooks
2012-05-10 12:40       ` Igor Grinberg
2012-05-10 16:15         ` Stephen Warren
2012-05-11  6:15           ` Igor Grinberg
2012-05-08 12:26   ` Linus Walleij
2012-05-09 17:12     ` Mark Brown
2012-05-04 19:50 ` Stephen Warren
2012-05-04 20:38   ` Wolfgang Denk
2012-05-04 20:59     ` Stephen Warren
2012-05-04 20:44   ` Mark Brown
2012-05-08 12:33     ` Linus Walleij
2012-05-09  8:41     ` Alessandro Rubini
2012-05-10 10:43   ` Ben Dooks
2012-05-10 16:11     ` Stephen Warren
2012-05-04 22:55 ` Russell King - ARM Linux
2012-05-04 23:40   ` Mark Brown
2012-05-04 23:52     ` Russell King - ARM Linux
2012-05-05  0:03       ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120504203357.6B79B206451@gemini.denx.de \
    --to=wd@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).