linux-kernel - Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160108194009.GM238@brightrain.aerifal.cx>
Date:	Fri, 8 Jan 2016 14:40:09 -0500
From:	Rich Felker <dalias@...c.org>
To:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc:	Rob Landley <rob@...dley.net>, Simon Horman <horms@...ge.net.au>,
	linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org,
	Yoshinori Sato <ysato@...rs.sourceforge.jp>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"D. Jeff Dionne" <jeff@...inux.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh
 sections

On Fri, Jan 08, 2016 at 08:28:51PM +0200, Laurent Pinchart wrote:
> > The current list is not a Renesas list, it is a Linux list for the
> > SuperH architecture port. Says so on the tin, and that was its history
> > until pretty recently. Renesas moving away from the SuperH architecture
> > doesn't change that this is the Linux arch/sh list.
> > 
> > We aren't proposing to rename the arch/sh directory to "jcore", so
> > "linux-sh@...r.kernel.org" remains the logical name for this list. The
> > new stuff is intentionally backwards compatible with the old stuff,
> 
> How about IP cores around the CPU, do you plan to develop cores compatible 
> with the Renesas implementations, or go for something else ? If we end up 
> sharing the same peripherals between multiple architectures we will need to 
> decide on how to coordinate the work.

To my knowledge, aside from the cpu which is of course ISA-compatible,
none of the current J-Core SOC components ("IP") are
interface-compatible with Renesas ones. I'm aiming to put as much as
possible in drivers/ rather than arch/sh/ because it should all be
shareable with other open-hardware cpus. We're already using uartlite
from drivers/ and I have some patches for it I still need to send
upstream, including SMP fixes and earlycon support.

> > and we are happy to maintain compatibility with the old stuff, and have
> > current plans to move it to device tree. (We just need a lot more legacy
> > test hardware...)
> 
> I personally don't think that's worth it given that most of the legacy 
> hardware is buried under a thick layer of dust (when not used as coasters or 
> door stoppers).

We probably need to gauge the level of interest in preserving support
for legacy hardware. I don't want to gratuitously drop anything, and I
think the device tree conversion will help us avoid that to some
extent by moving the bulk of hardware/board support from code to data,
but I will need to find a way to get my hands on some of the old
hardware if we want to verify that I'm not breaking it.

Another consideration is what qemu emulates, which right now is the
legacy hardware. After J2 support, my first sh kernel priority is
getting to the point where it can boot in qemu-system-sh4 using device
tree, and where qemu can be configured based on a device tree, so that
we can actually provide a reasonable amount of ram to run a modern
system. I know Rob is interested in this to be able to test full
system builds, native compiling, etc.

Rich