lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 1 Feb 2010 23:26:05 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Pavel Machek <pavel@....cz>
Cc:	Magnus Damm <magnus.damm@...il.com>, linux@....linux.org.uk,
	eric.y.miao@...il.com, tony@...mide.com,
	linux-kernel@...r.kernel.org, khilman@...prootsystems.com,
	ben-linux@...ff.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 01/06] ARM: SuperH Mobile ARM, sh7367 and G3EVM support

On Mon, Feb 01, 2010 at 03:10:57PM +0100, Pavel Machek wrote:
> > This patch contains the SuperH Mobile ARM base support together
> > with sh7367 CPU and G3EVM board support. Only timer, serial
> > console and NOR flash are supported at this point. Patches for
> > the interrupt controller, pinmux support, clock framework and
> > runtime pm will be submitted as feature patches on top of this.
> ...
> >  arch/arm/mach-shmobile/Makefile.boot              |    9 
> >  arch/arm/mach-shmobile/board-g3evm.c              |  127 +++++++++++
> 
> I guess I'm confused. I thought superh was architecture, like arm
> is.....?
> 
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. There are some SH-Mobiles that are SH-only, and those are taken
care of in arch/sh/ as normal. Most of the shared code sits in drivers/sh
and so forth, requiring fairly little glue on the ARM architecture side.
As support for these CPUs is extended, we'll likely see more of arch/sh/
being generalized. There's likely not going to be enough that is directly
reusable between the two to warrant a split out architecture directory of
its own, but we'll see how it goes.

It's forseeable that we will also see support for the same CPU in
arch/sh/ aimed at the SH MPU, and that we can have linux running on both
the SH and the ARM at the same time sharing the same peripheral domain.
However, all of these things are out of scope for this patch set, which
is just getting the groundwork established for the ARM MPU.

> I superh actually manufacturer? And can we get shorter name than
> mach-shmobile? mach-shm?

shmobile is what the line is called, and matches the naming scheme we
already have in-tree today. Changing that around would only lead to more
confusion. It's also not really any longer than many of the other mach
types, so I don't really see the point.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ