From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] ARM: mxc: don't allow to compile together i.MX51 and i.MX53
Date: Mon, 11 Apr 2011 09:40:41 +0200 [thread overview]
Message-ID: <20110411074041.GF18601@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1104102157440.28032@xanadu.home>
On Sun, Apr 10, 2011 at 10:02:03PM -0400, Nicolas Pitre wrote:
> On Sun, 10 Apr 2011, Uwe Kleine-K?nig wrote:
>
> > The two SoCs have different PHYS_OFFSETs so it's not (yet) possible to
> > compile a single (working) kernel for these.
>
> Really?
>
> Have a look at CONFIG_ARM_PATCH_PHYS_VIRT. It's in mainline and fully
> functional.
I'm aware of this config item. But still if it's off there must be a
distinction that's provided by this patch. Currently you can build a
kernel for i.MX51 + i.MX53 but IIRC it works on no machine.
When considering ARM_PATCH_PHYS_VIRT there are more SoCs that could be
built into a single image and so needs a more complicated logic.
And I don't want to depend on ARM_PATCH_PHYS_VIRT (yet), e.g. because
it's new and still depends on EXPERIMENTAL.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-04-11 7:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 19:48 [PATCH 1/6] ARM: mxc: update defconfigs Uwe Kleine-König
2011-04-10 19:48 ` [PATCH 2/6] ARM: mxc: don't use the symbols in the CPU family choice to select others Uwe Kleine-König
2011-04-10 19:49 ` [PATCH 3/6] ARM: mxc: simplify platform selection for i.MX21 and i.MX27 Uwe Kleine-König
2011-04-10 19:49 ` [PATCH 4/6] ARM: mxc: don't allow to compile together i.MX51 and i.MX53 Uwe Kleine-König
2011-04-11 2:02 ` Nicolas Pitre
2011-04-11 7:40 ` Uwe Kleine-König [this message]
2011-04-11 14:15 ` Nicolas Pitre
2011-04-11 21:50 ` Matt Sealey
2011-04-12 8:52 ` Russell King - ARM Linux
2011-04-12 6:38 ` Uwe Kleine-König
2011-04-12 9:54 ` Uwe Kleine-König
2011-04-12 20:27 ` Russell King - ARM Linux
2011-04-12 20:37 ` Uwe Kleine-König
2011-04-12 20:53 ` Russell King - ARM Linux
2011-04-12 21:12 ` [PATCH] ARM: remove ns9xxx port Uwe Kleine-König
2011-04-26 21:53 ` Uwe Kleine-König
2011-04-26 22:13 ` Russell King - ARM Linux
2011-04-12 21:20 ` [PATCH 4/6] ARM: mxc: don't allow to compile together i.MX51 and i.MX53 Uwe Kleine-König
2011-04-12 22:54 ` Nicolas Pitre
2011-04-13 6:20 ` Uwe Kleine-König
2011-04-12 9:16 ` Jason Liu
2011-04-12 9:45 ` Uwe Kleine-König
2011-04-13 2:28 ` Nicolas Pitre
2011-04-13 12:25 ` Shawn Guo
2011-04-13 12:41 ` Uwe Kleine-König
2011-05-04 15:48 ` Matt Sealey
2011-05-04 15:56 ` Matt Sealey
2011-05-04 16:04 ` Uwe Kleine-König
2011-05-08 10:42 ` Russell King - ARM Linux
2011-05-08 15:00 ` Nicolas Pitre
2011-05-08 15:05 ` Russell King - ARM Linux
2011-05-08 15:23 ` Nicolas Pitre
2011-04-13 13:39 ` Jason Liu
2011-04-10 19:49 ` [PATCH 5/6] ARM: mx3: make ioremap quirk ready for multi-SoC kernels Uwe Kleine-König
2011-04-10 19:49 ` [PATCH 6/6] ARM: imx: remove some deprecated and unused #defines Uwe Kleine-König
2011-04-12 7:59 ` [PATCH 1/6] ARM: mxc: update defconfigs Shawn Guo
2011-04-12 8:08 ` Uwe Kleine-König
2011-04-12 8:19 ` [PATCH v2] " Uwe Kleine-König
2011-04-12 8:33 ` [PATCH 1/6] " Shawn Guo
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=20110411074041.GF18601@pengutronix.de \
--to=u.kleine-koenig@pengutronix.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).