linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] arm: add documentation describing Marvell families of SoC
Date: Sat, 4 Aug 2012 23:01:59 +0200	[thread overview]
Message-ID: <20120804230159.12f7108a@skate> (raw)
In-Reply-To: <alpine.LFD.2.02.1207171452250.9293@xanadu.home>

Hello Nicolas,

Le Tue, 17 Jul 2012 14:58:12 -0400 (EDT),
Nicolas Pitre <nico@fluxnic.net> a ?crit :

> > I think I have an old list that was compiled by Lennert.  I'll try to 
> > dig it out in case this document could benefit from it.
> 
> Here's what I've dug out. This is dated October 2007.
> 
> ----- >8
> 
> family			out of order			in order
> ==============================================================================
> no mmu		|				|			     |
> no cache	|	Falcon			|	Falcon D	     |
> "966"		|				|	a.k.a. Dragonite     |
> ==============================================================================
> no mmu		|				|			     |
> cache		|	Osprey			|	Osprey D	     |
> "946"		|				|			     |
> ==============================================================================
> 		|	single issue: Mohawk	|			     |
> mmu		|	a.k.a. Feroceon 1850	|			     |
> cache		|	a.k.a. Feroceon FR-331	|	single issue:	     |
> "926"		|				|	Mohawk D	     |
> 		|	dual issue: Jolteon	|			     |
> 		|	a.k.a. Feroceon 2850	|			     |
> ==============================================================================
> 
> Variants:
> - Falcon DMC - Multi-Core version of the Falcon D
> - Falcon DMT - Multi-Thread version of the Falcon D
> - Osprey DMT - Multi-Thread version of Osprey D
> 
> There is also the Flareon, which is what will be used in Dove:
> - Based on the Jolteon
> - v6/v7 support
> - packaged with L2, VFP, AXI
> 
> All of these cores can be mixed-and-matched with L2, VFP, AXI, wMMXt,
> etc.

Thanks for those details. However, I'm not really able to match those
details against the Marvell SoCs themselves. Could you detail which ARM
core corresponds to which Marvell SoC family, or specific model?

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-08-04 21:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 14:26 [PATCH] [RFC] arm: add documentation describing Marvell families of SoC Thomas Petazzoni
2012-07-17 14:59 ` Andrew Lunn
2012-07-17 15:37   ` Thomas Petazzoni
2012-07-17 15:09 ` Arnd Bergmann
2012-07-17 15:40   ` Thomas Petazzoni
2012-07-17 16:52     ` Andrew Lunn
2012-07-17 15:45   ` Nicolas Pitre
2012-07-17 18:58     ` Nicolas Pitre
2012-08-04 21:01       ` Thomas Petazzoni [this message]
2012-07-17 15:35 ` [PATCH v2] " Thomas Petazzoni
2012-07-17 18:01 ` [PATCH] " Eric Miao
2012-07-17 18:05   ` Andrew Lunn
2012-07-17 18:08     ` Eric Miao
2012-07-17 18:35   ` Thomas Petazzoni
2012-07-17 18:50     ` Eric Miao
2012-08-04 20:59   ` Thomas Petazzoni

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=20120804230159.12f7108a@skate \
    --to=thomas.petazzoni@free-electrons.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 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).