From: Andreas Schweigstill <andreas@schweigstill.de>
To: linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: RFC: rename arch/arm/mach-s3c2410 to arch/arm/mach-s3c24xx
Date: Thu, 20 Apr 2006 12:37:34 +0200 [thread overview]
Message-ID: <4447646E.2080008@schweigstill.de> (raw)
In-Reply-To: <20060419150527.GA4102@flint.arm.linux.org.uk>
Hi Russell!
Russell King schrieb:
> Folk convinced me that the only thing which we should call "architecture"
> is the CPU - so things like "PPC", "ARM", "i386" are architectures, and
> not implementations of these (AT91RM9200, S3C2410).
And if we use ARM nomenclature there is also a difference between the
architecture (e.g. v4, v4t, v5, ...) and the implementation (ARM7,
ARM7T, ARM9T, Amulet, StrongARM, Xscale, ...) of the CPU core.
So we have to distinguish between the core and the SoC/ASSP
architecture. The register model is defined by the core architecture
but the co-processors (MMU, CP15) by the implementation. And should we
handle OMAP as a standard ARM9/10/11 implementation or another core?
And should StrongARM be inherited from v4 or ARM8?
Does it make sense to reflect this also in the directory naming
conventions? Hmmm, I am not sure. We could end with the complete ARM
company's history.
With best regards
Andreas Schweigstill
--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
prev parent reply other threads:[~2006-04-20 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060418165204.GG2516@trinity.fluff.org>
2006-04-19 11:01 ` RFC: rename arch/arm/mach-s3c2410 to arch/arm/mach-s3c24xx Dimitry Andric
2006-04-19 11:20 ` Komal Shah
2006-04-19 14:40 ` Bill Gatliff
2006-04-19 15:05 ` Russell King
2006-04-20 10:37 ` Andreas Schweigstill [this message]
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=4447646E.2080008@schweigstill.de \
--to=andreas@schweigstill.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.