public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600	CPU and MVF600TWR board support
Date: Tue, 21 May 2013 18:27:32 +0200 (CEST)	[thread overview]
Message-ID: <264205853.1016550.1369153652659.JavaMail.root@advansee.com> (raw)
In-Reply-To: <1369126981-13970-1-git-send-email-b18965@freescale.com>

Hi Alison,

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.

> 
> The u-boot runs on Cortex A5 core.

[...]

Best regards,
Beno?t

  parent reply	other threads:[~2013-05-21 16:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  9:02 [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support Alison Wang
2013-05-21  9:02 ` [U-Boot] [PATCH v3 1/6] arm: mvf600: Add Vybrid MVF600 CPU support Alison Wang
2013-05-21 13:48   ` Fabio Estevam
2013-05-22  2:59     ` Wang Huan-B18965
2013-05-21 16:57   ` Benoît Thébaudeau
2013-05-22  5:17     ` Wang Huan-B18965
2013-05-21 19:00   ` Benoît Thébaudeau
2013-05-22  5:30     ` Wang Huan-B18965
2013-05-21  9:02 ` [U-Boot] [PATCH v3 2/6] arm: mvf600: Add IOMUX support for Vybrid MVF600 Alison Wang
2013-05-21 17:10   ` Benoît Thébaudeau
2013-05-21  9:02 ` [U-Boot] [PATCH v3 3/6] net: fec_mxc: Add " Alison Wang
2013-05-21 17:15   ` Benoît Thébaudeau
2013-05-21  9:02 ` [U-Boot] [PATCH v3 4/6] arm: mvf600: Add watchdog " Alison Wang
2013-05-21  9:03 ` [U-Boot] [PATCH v3 5/6] arm: mvf600: Add uart " Alison Wang
2013-05-21  9:03 ` [U-Boot] [PATCH v3 6/6] arm: mvf600: Add basic support for Vybrid MVF600TWR board Alison Wang
2013-05-21 17:29   ` Benoît Thébaudeau
     [not found]     ` <81BA6E5E0BC2344391CABCEE22D1B6D8335B27@039-SN1MPN1-003.039d.mgd.msft.net>
2013-05-22 16:21       ` Benoît Thébaudeau
2013-05-23  5:44         ` Wang Huan-B18965
2013-05-21 19:19   ` Benoît Thébaudeau
2013-05-21 16:27 ` Benoît Thébaudeau [this message]
     [not found]   ` <81BA6E5E0BC2344391CABCEE22D1B6D8335A6C@039-SN1MPN1-003.039d.mgd.msft.net>
2013-05-23 17:09     ` [U-Boot] [PATCH v3 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support Benoît Thébaudeau
2013-05-24  6:18       ` Wang Huan-B18965
2013-05-27  6:51         ` Stefano Babic
2013-05-28  8:51           ` Wang Huan-B18965
2013-05-28  9:03             ` Stefano Babic
2013-05-28  8:59         ` Wang Huan-B18965
  -- strict thread matches above, loose matches on Subject: below --
2013-05-22  5:08 Wang Huan-B18965

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=264205853.1016550.1369153652659.JavaMail.root@advansee.com \
    --to=benoit.thebaudeau@advansee.com \
    --cc=u-boot@lists.denx.de \
    /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