linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] base board consolidation
Date: Mon, 4 Jul 2011 09:27:22 +0100	[thread overview]
Message-ID: <20110704082722.GM21898@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110701094403.GT11559@pengutronix.de>

On Fri, Jul 01, 2011 at 11:44:03AM +0200, Uwe Kleine-K?nig wrote:
> At some time this will probably be obsoleted by device tree stuff, the
> upside of this approach is that it already works today without the need
> to adapt the bootloader.

The other issue is that the reverse is also true - platforms can be a
common baseboard, and its the CPU tile which changes.  That's standard
for the ARM development boards.

While the CPU tiles for platforms before Versatile Express had very
little variance other than the actual CPU, Versatile Express can have
dramatically different physical address maps depending on the CPU tile
fitted.  The only real common thing is the offsets for peripherals
within each chip select region.

As also said, all this should be solved by DT, so I don't see there's
much point in creating this abstraction just to have it obsoleted
shortly thereafter.  Much better to put that effort into ensuring that
DT can handle these setups...

  parent reply	other threads:[~2011-07-04  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  9:44 [RFC PATCH 0/3] base board consolidation Uwe Kleine-König
2011-07-01  9:46 ` [RFC PATCH 1/3] ARM: common abstraction for specifying a baseboard Uwe Kleine-König
2011-07-01  9:46   ` [RFC PATCH 2/3] ARM: imx/mx31moboard: convert to new baseboard handling Uwe Kleine-König
2011-07-01  9:46   ` [RFC PATCH 3/3] ARM: imx/mx31moboard: remove obsolete " Uwe Kleine-König
2011-07-04  8:19 ` [RFC PATCH 0/3] base board consolidation Philippe Rétornaz
2011-07-04  8:27 ` Russell King - ARM Linux [this message]
2011-07-04 10:20   ` Daniel Mack
2011-07-04 10:38     ` Russell King - ARM Linux
2011-07-04 11:55       ` Marek Vasut
2011-07-04 12:33         ` Russell King - ARM Linux

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=20110704082722.GM21898@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).