mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	horms@verge.net.au, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Rob Herring <rob.herring@calxeda.com>,
	rjw@sisk.pl, lethal@linux-sh.org, olof@lixom.net,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 03/03] ARM: Undelete KZM9D mach-type
Date: Tue, 15 May 2012 19:09:47 +0000	[thread overview]
Message-ID: <201205151909.47381.arnd@arndb.de> (raw)
In-Reply-To: <20120515175609.04A4D3E080A@localhost>

On Tuesday 15 May 2012, Grant Likely wrote:
> On Tue, 15 May 2012 08:32:09 +0000, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Monday 14 May 2012, Magnus Damm wrote:
> > > Right, I agree. Relying on a fixed DTB in an unreliable boot loader is
> > > the last thing I want to do.
> > > 
> > > So if your boot loader can't pass DTB to the kernel, and you want to
> > > have a single kernel supporting multiple boards, then do you see
> > > anything wrong with based on mach-type do a run time decision (in
> > > arch/arm/boot/compressed/) to override the ATAG from the boot loader
> > > with a compiled-in per-board DTB?
> > 
> > I know that we have discussed this in the past, but I don't remember
> > the outcome of the discussion, maybe someone else can help out here
> > (Grant?)
> > 
> > It's definitely technically possible to do it, but it could either be
> > that nobody has bothered to do the implementation, or that we had good
> > reasons against it and decided not to allow this.
> 
> Tony and I talked about this quite a bit during the last Connect.  The
> plan is to extend the existing bootwrapper ATAGs to DT code to allow
> appending multiple .dtbs to the zImage and selecting the correct one
> based on the machine number.  It shouldn't be very complicated, but I
> haven't had time to implement it.

Ok, good. so you are both on the same page then, Grant and Magnus.
I suppose you just need to coordinate then who is doing the work,
and it seems that Magnus is eager to prototype this.

	Arnd

      reply	other threads:[~2012-05-15 19:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 10:54 [PATCH 00/03] ARM: mach-shmobile: DT_MACHINE and mach-type updates Magnus Damm
2012-05-14 10:54 ` [PATCH 01/03] mach-shmobile: Use DT_MACHINE for KZM9G Magnus Damm
2012-05-14 10:54 ` [PATCH 02/03] mach-shmobile: Use DT_MACHINE for armadillo 800 eva Magnus Damm
2012-05-14 10:54 ` [PATCH 03/03] ARM: Undelete KZM9D mach-type Magnus Damm
2012-05-14 12:30   ` Russell King - ARM Linux
2012-05-14 20:49     ` Magnus Damm
2012-05-14 21:07       ` Arnd Bergmann
2012-05-14 21:45         ` Magnus Damm
2012-05-15  8:32           ` Arnd Bergmann
2012-05-15 16:34             ` Magnus Damm
2012-05-15 19:50               ` Arnd Bergmann
2012-05-15 17:56             ` Grant Likely
2012-05-15 19:09               ` Arnd Bergmann [this message]

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=201205151909.47381.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=grant.likely@secretlab.ca \
    --cc=horms@verge.net.au \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=olof@lixom.net \
    --cc=rjw@sisk.pl \
    --cc=rob.herring@calxeda.com \
    /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

Powered by JetHome