From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] arm/imx: merge i.MX3 and i.MX6
Date: Thu, 29 Sep 2011 10:35:13 +0200 [thread overview]
Message-ID: <20110929083512.GC31404@pengutronix.de> (raw)
In-Reply-To: <20110929051725.GA19318@S2100-06.ap.freescale.net>
On Thu, Sep 29, 2011 at 01:17:28PM +0800, Shawn Guo wrote:
> On Wed, Sep 28, 2011 at 02:18:08PM +0200, Sascha Hauer wrote:
> > On Wed, Sep 28, 2011 at 05:16:08PM +0800, Shawn Guo wrote:
> > >
> > >
> > > -config ARCH_MX3
> > > - bool "MX3-based"
> > > +config ARCH_IMX_V6_V7
> > > + bool "i.MX3, i.MX6"
> > > + select AUTO_ZRELADDR
> > > + select ARM_PATCH_PHYS_VIRT
> >
> > Russell pointed out that it's not a good idea to select this.
> >
> Yeah, I saw that. So you would support ZBOOT_ROM over single zImage
> between these two? I'm not sure how many imx users are actually using
> ZBOOT_ROM. If there are only very few, we still want to keep the
> default configuration compatible with ZBOOT_ROM? I think we can move
> the default build to single zImage, and let those limited users sort
> out their own configuration to get ZBOOT_ROM back. After all, the
> support is still there, and it's just about build configuration
> adjustment.
I'm not sure there are i.MX ZBOOT_ROM users at all. Anyway,
select AUTO_ZRELADDR if !ZBOOT_ROM
seems to work.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-09-29 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 9:16 [PATCH 0/6] Support single zImage for imx3 and imx6 Shawn Guo
2011-09-28 9:16 ` [PATCH 1/6] arm/imx: merge mm-imx35.c into mm-imx31.c Shawn Guo
2011-09-28 9:16 ` [PATCH 2/6] arm/imx: rename mm-imx31.c to mm-imx3.c Shawn Guo
2011-09-28 9:16 ` [PATCH 3/6] arm/imx: change mxc_init_l2x0() to an imx31/35 specific call Shawn Guo
2011-09-28 9:16 ` [PATCH 4/6] arm/imx: remove cpu_is_xxx() from arch_idle() Shawn Guo
2011-09-29 8:59 ` Sascha Hauer
2011-09-29 14:22 ` Shawn Guo
2011-09-28 9:16 ` [PATCH 5/6] arm/imx: remove cpu_is_xxx() check from __imx_ioremap() Shawn Guo
2011-09-28 9:16 ` [PATCH 6/6] arm/imx: merge i.MX3 and i.MX6 Shawn Guo
2011-09-28 12:18 ` Sascha Hauer
2011-09-29 5:17 ` Shawn Guo
2011-09-29 8:35 ` Sascha Hauer [this message]
2011-09-28 12:20 ` [PATCH 0/6] Support single zImage for imx3 and imx6 Sascha Hauer
2011-09-29 5:19 ` 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=20110929083512.GC31404@pengutronix.de \
--to=s.hauer@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).