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] [day] [month] [year] [list]
Message-ID: <CANqRtoTamkCfu0yHiF8oGXdLKDjSxhBO-GqPDJ00Ejw5LkSqkw@mail.gmail.com>
Date:	Wed, 9 May 2012 17:12:52 +0900
From:	Magnus Damm <magnus.damm@...il.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Arnd Bergmann <arnd@...db.de>, "Rafael J. Wysocki" <rjw@...k.pl>,
	linux-arm-kernel@...ts.infradead.org, horms@...ge.net.au,
	linux@....linux.org.uk, linux-sh@...r.kernel.org,
	linux-kernel@...r.kernel.org, lethal@...ux-sh.org, olof@...om.net
Subject: Re: [PATCH 00/02] mach-shmobile: Emma Mobile EV2 - first shot

On Wed, May 9, 2012 at 4:57 PM, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Sat, May 5, 2012 at 9:21 PM, Arnd Bergmann <arnd@...db.de> wrote:
>> On Saturday 05 May 2012, Rafael J. Wysocki wrote:
>>> Now, if you insist on us having a separate mach- directory for every platform
>>> (SoC), we can do that I think, but then we should start with splitting up the
>>> existing mach-shmobile into a number of SoC-specific directories rather than
>>> adding new mach- directories for random new parts, because that goes against
>>> our development history to date, which is important too IMHO.
>>
>> All the chips in there so far share a common ancestry and they all use a
>> significant subset of the same drivers shared with arch/sh: i2c-sh_mobile,
>> sh-dma-engine, sh_cmt, sh-sci, sh_tmu, intc, pfc and sh_clk. AFAICT, this one
>> uses none of those and apparently was developed by NEC before the merger with
>> Renesas.
>
> Ah, I didn't know NEC joined Renesas, but Wikipedia proves you're right.

Actually, for those of you who care about details - NEC Electronics
and Renesas merged into Renesas Electronics. Other parts of NEC are
still around as usual.

> So, any similarities with the MIPS-based NEC EMMA SOCs, i.e. more code to
> share?

That would be very interested to know. I've grepped the kernel tree
for existing code matching Uart, STI and GPIO but nothing so far. Does
anyone know where I can find docs for the MIPS based ones?

Good news is that documentation for Emma Mobile EV2 and Emma Mobile
1-S can be downloaded from renesas.com.

Cheers,

/ magnus
--
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