From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Pavel Machek <pavel@ucw.cz>, Magnus Damm <magnus.damm@gmail.com>,
linux@arm.linux.org.uk, eric.y.miao@gmail.com, tony@atomide.com,
linux-kernel@vger.kernel.org, khilman@deeprootsystems.com,
ben-linux@fluff.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/06] ARM: SuperH Mobile ARM, sh7367 and G3EVM support
Date: Mon, 1 Feb 2010 17:19:21 +0100 [thread overview]
Message-ID: <63386a3d1002010819r63aae9edn2f5bc7e7f08a5fdf@mail.gmail.com> (raw)
In-Reply-To: <20100201142605.GB13428@linux-sh.org>
2010/2/1 Paul Mundt <lethal@linux-sh.org>:
> SH-Mobile (G series, in this case) is a line of SH/ARM multi-cores. They
> contain both SH and ARM MPUs and are built up almost entirely on SH IP
> blocks.
Jaysis, that's one odd bird. There must be some upside to designing
things like this, is there some paper or conference presentation on the idea
behind this thing somewhere out there? I just get very curious!
Linus Walleij
next prev parent reply other threads:[~2010-02-01 16:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 12:40 [PATCH 00/06] ARM: Initial SuperH Mobile ARM support Magnus Damm
2010-01-28 12:40 ` [PATCH 01/06] ARM: SuperH Mobile ARM, sh7367 and G3EVM support Magnus Damm
2010-01-28 22:08 ` Russell King - ARM Linux
2010-01-29 11:26 ` Magnus Damm
2010-02-01 14:10 ` Pavel Machek
2010-02-01 14:26 ` Paul Mundt
2010-02-01 16:19 ` Linus Walleij [this message]
2010-02-02 0:12 ` Paul Mundt
2010-01-28 12:40 ` [PATCH 02/06] ARM: Add sh7377 and G4EVM support Magnus Damm
2010-01-28 12:41 ` [PATCH 03/06] ARM: Add sh7372 and AP4EVB support Magnus Damm
2010-01-28 22:19 ` Russell King - ARM Linux
2010-01-28 12:41 ` [PATCH 04/06] sh: Build drivers/sh for SuperH Mobile ARM Magnus Damm
2010-01-28 12:41 ` [PATCH 05/06] sh: Let INTC set IRQF_VALID on ARM platforms Magnus Damm
2010-01-29 2:50 ` Paul Mundt
2010-01-28 12:41 ` [PATCH 06/06] sh-sci: Preliminary SuperH Mobile ARM support Magnus Damm
2010-01-29 2:52 ` Paul Mundt
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=63386a3d1002010819r63aae9edn2f5bc7e7f08a5fdf@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=ben-linux@fluff.org \
--cc=eric.y.miao@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®