linux-kernel - Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family

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]

Message-ID: <20160725202209.5fae4d98@free-electrons.com>
Date:	Mon, 25 Jul 2016 20:22:09 +0200
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	Rob Herring <robh@...nel.org>
Cc:	Grzegorz Jaszczyk <jaz@...ihalf.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Mark Rutland <mark.rutland@....com>,
	Jason Cooper <jason@...edaemon.net>,
	Andrew Lunn <andrew@...n.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Russell King - ARM Linux <linux@...linux.org.uk>,
	Gregory CLEMENT <gregory.clement@...e-electrons.com>,
	Marcin Wojtas <mw@...ihalf.com>,
	Lior Amsalem <alior@...vell.com>
Subject: Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC
 family

Hello,

On Mon, 25 Jul 2016 10:12:43 -0500, Rob Herring wrote:

> Yes, I get that, but that is only meaningful if you want to run an OS
> that is only aware of 395 on a 398 SoC/board (though I'd guess the 390
> compat is enough for that). Otherwise, that property is not really
> meaningful as the additional nodes are enough to handle what is the
> superset.
> 
> I would agree both are fine if both chips are in fact the same die,
> just fused or packaged differently. I've seen a lot of chips that are
> supposed to be sub/supersets of each other, but have different errata
> lists because they are different die.

Unfortunately HW vendors are rarely willing to publicly indicate whether
the different chips in their families are actually the same die fused
differently, or really different dies.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com