[U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support

[Wang Huan-B18965 <B18965@freescale.com>]

Hi, Benoit,

On Tuesday, May 21, 2013 11:02:55 AM, Alison Wang wrote:
> This series contain the support for Freescale Vybrid MVF600 CPU and MVF600TWR
> board.
>
> Vybird devices are built on an asymmetrical-multiprocessing architecture
> using ARM cores. The families in the Vybrid portfolio span entry-level,
> single core Cortex-A class SoCs all the way to dual heterogeneous core SoCs
> with multiple communication and connectivity options.
>
> Part of the Vybrid platform, MVF600 is a dual-core eMPU combining the ARM
> Cortex A5 and Cortex M4 cores.
>
> MVF600 shares some IPs with i.MX family, such as FEC,ESDHC,WATCHDOG,I2C,ASRC
> and ESAI.
> MVF600 also shares some IPs with ColdFire family, such as eDMA and DSPI.
> MVF600 still has its own IPs, such as PIT,SAI,UART,QSPI and DCU.
>
> More documents for this soc can be found at:
> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=VF6xx&fsrch=1&sr=5
> http://www.freescale.com/webapp/sps/site/homepage.jsp?code=VYBRID

I have a question about the naming of this SoC. On Freescale's website, it is
VF6xx everywhere, but you add a leading M (_M_VF600). Is it because you are
using an internal SoC name known only by Freescale and different from the
marketing SoC name, or is this M from the part number, or will the marketing SoC
name change later, or some other reason? Please clarify. U-Boot users must be
able to identify a SoC and to find information about it easily.
[Alison Wang] We always use the name "MVF600" in the internal development.
We will check it with marketing team, and confirm it. Thanks.
>
> The u-boot runs on Cortex A5 core.

[...]

Best regards,
Alison Wang