All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX multi SoC patches
Date: Wed, 31 Aug 2011 22:05:28 +0800	[thread overview]
Message-ID: <20110831140527.GA3723@S2100-06.ap.freescale.net> (raw)
In-Reply-To: <CAODfWeFnsQZBsBXpJLVknzvqcythZjDMyfe8sb9Pdw_uK-iB2g@mail.gmail.com>

On Wed, Aug 31, 2011 at 02:02:58PM +0100, Hector Oron wrote:
> Hello,
> 
> 
> 2011/8/24 Sascha Hauer <s.hauer@pengutronix.de>:
> > This is hopefully the last iteration of the patches for compiling
> > all ARMv4/v5 based i.MXs together. CONFIG_ARM_PATCH_PHYS_VIRT
> > lost its experimental status and we can still build uImages
> > even with CONFIG_AUTO_ZRELADDR enabled. This series selects
> > these options and makes a multi SoC image the default.
> > Also, we can now build all i.MX5 SoCs into a single image.
> > This series also updates the defconfigs.
> 
> On a mx53 loco board I have rebased Richard's patchset for SATA and
> got it running, but I see this on mapping on iomem, board is more or
> less working but I was unsure if this is something significant or just
> some ugly cosmetic names for mx53 (i.e. imx21-uart.0, imx31-gpio, ..)
> 
This is expected.  The platform_device_id had been used to kill
cpu_is_mxXX() stuff from drivers.  And we decided to use soc prefix
to define IP block version in platform_device_id table, because
hardware does not define revisions, and soc is stable enough to
identify specific IP block version.

-- 
Regards,
Shawn

      reply	other threads:[~2011-08-31 14:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  8:03 i.MX multi SoC patches Sascha Hauer
2011-08-24  8:03 ` [PATCH 1/4] ARM i.MX: allow to compile together ARMv4 and ARMv5 based SoCs Sascha Hauer
2011-08-24  8:03 ` [PATCH 2/4] ARM i.MX: allow to compile together all i.MX5 " Sascha Hauer
2011-08-24  8:03 ` [PATCH 3/4] ARM i.MX5: update defconfig Sascha Hauer
2011-08-24  8:03 ` [PATCH 4/4] ARM i.MX defconfigs: use one defconfig for all ARMv4/v5 SoCs Sascha Hauer
2011-08-24 23:03 ` i.MX multi SoC patches Hector Oron
2011-08-25  6:38   ` Sascha Hauer
2011-08-25 11:44   ` hector.oron at gmail.com
2011-08-25 11:44     ` [PATCH] ARM: mx5: fix remaining unconsistent names for irqs hector.oron at gmail.com
2011-08-25 11:52     ` i.MX multi SoC patches Hector Oron
2011-08-25 12:55   ` [PATCH] ARM: mx5: fix remaining unconsistent names for irqs hector.oron at gmail.com
2011-08-25 14:16     ` Arnaud Patard (Rtp)
2011-08-25 14:54     ` Sascha Hauer
2011-08-31 13:02 ` i.MX multi SoC patches Hector Oron
2011-08-31 14:05   ` Shawn Guo [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=20110831140527.GA3723@S2100-06.ap.freescale.net \
    --to=shawn.guo@freescale.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.