From: DJ Delorie <dj@redhat.com>
To: dhowells@redhat.com
Cc: linux-am33-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #2]
Date: Tue, 30 Oct 2007 13:47:28 -0400 [thread overview]
Message-ID: <200710301747.l9UHlSMH016352@greed.delorie.com> (raw)
In-Reply-To: <27157.1193763218@redhat.com> (message from David Howells on Tue, 30 Oct 2007 16:53:38 +0000)
> They can if they're told so, plus if they've got the CPU docs to
> hand, it should be more obvious. The AM33 is a variant of the
> MN10300 arch as far as I can tell.
Right, there's also the AM30, AM31, AM32, and AM34. Panasonic calls
the whole series the "AM3" or "MN103 series" although they also have
MN103E and MN103S series. MN103E is the AM33/AM34 microprocessors
(MMU), MN103S is the AM3[012] microcontrollers (no MMU).
http://www.semicon.panasonic.co.jp/e-micom/MicomFamily/roadmap.html
next prev parent reply other threads:[~2007-10-30 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 12:27 David Howells
2007-10-29 12:28 ` [PATCH 1/2] MN10300: Suppress AOUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT " David Howells
2007-10-30 12:57 ` [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel " Suzuki Takashi
2007-10-30 14:14 ` David Howells
2007-10-30 15:10 ` Suzuki Takashi
2007-10-30 16:53 ` David Howells
2007-10-30 17:47 ` DJ Delorie [this message]
2007-10-30 21:59 ` Suzuki Takashi
2007-10-30 23:06 ` David Howells
2007-10-31 10:50 ` Alan Cox
2007-11-02 15:19 ` Suzuki Takashi
[not found] ` <20071029122809.2846.58795.stgit@warthog.procyon.org.uk>
2007-10-30 14:40 ` [Linux-am33-list] [PATCH 2/2] MN10300: Add the MN10300/AM33 architecture to the " Suzuki Takashi
2007-10-30 20:04 ` David Howells
2007-10-31 0:03 ` Suzuki Takashi
2007-10-31 11:46 ` David Howells
2007-11-03 16:07 ` Suzuki Takashi
2007-11-05 15:38 ` David Howells
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=200710301747.l9UHlSMH016352@greed.delorie.com \
--to=dj@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®