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:	Fri, 8 Jan 2016 21:35:11 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Rich Felker <dalias@...c.org>
Cc:	Simon Horman <horms@...ge.net.au>,
	Linux-sh list <linux-sh@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Yoshinori Sato <ysato@...rs.sourceforge.jp>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"D. Jeff Dionne" <jeff@...inux.org>, Rob Landley <rob@...dley.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections

Hi Rich,

On Fri, Jan 8, 2016 at 7:21 PM, Rich Felker <dalias@...c.org> wrote:
> On Fri, Jan 08, 2016 at 10:01:25AM +0100, Geert Uytterhoeven wrote:
>> Many old ARM/SH-Mobile SoCs look like SH SoCs with an ARM CPU core bolted on.
>> Recent Renesas ARM SoCs still share many IP cores with older SH SoCs; most of
>> them even have a secondary SH4 CPU core. Using the SH4 CPU core could be useful
>> for doing SH4 work, until J4 becomes mainstream (cfr. old prototype in
>> http://www.spinics.net/lists/linux-sh/msg07188.html).
>> Probably the Jx series won't share IP cores with SH/ARM, but as arch/sh/
>> maintainers you have to care about older Renesas SH platforms, too.
>>
>> For patchwork, that would mean some more delegation needs to be put in place.
>>
>> So far my 0.05€...
>
> Is that actually the case? I can't find any current support in the
> kernel for running on these SH4 cores, and I was under the impression
> that they were being phased out, if not already gone. And the bulk of

There's no in-kernel support for these SH4 cores yet, just the prototype.

> the driver-related discussion I've seen on linux-sh over the past year
> does not seem to be related to hardware that's present/usable on
> boards where you can run Linux/SH. If this is incorrect, I'd like to
> hear some views on how/why such hardware is relevant to arch/sh.

At least the following drivers are shared between ARM and SH:

hspi
rspi
sh-cmt
sh_fsi
sh-mtu2
sh-sci (covering sci, scif, scifa, scifb, hscif)
sh-tmu
tpu

and of course the sh-pfc pinctrl subsystem.

Probably I'm forgetting a few that haven't been converted to DT on ARM yet,
and where the ARM side thus could benefit from a DT conversion on SH.

Note that you can find "shmobile" SoCs under both arch/sh/
(sh7723/sh7724/sh7343/sh7722/sh7366) and arch/arm/mach-shmobile/.
Some of these used to share even more code (e.g. drivers/sh/clk/), until the
ARM ones were converted to the Common Clock Framework.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ