From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ralf Baechle Subject: Re: [Ksummit-2009-discuss] Representing Embedded Architectures at the Kernel Summit Date: Wed, 3 Jun 2009 08:07:39 +0100 Message-ID: <20090603070739.GD23561@linux-mips.org> References: <1243956140.4229.25.camel@mulgrave.int.hansenpartnership.com> <20090602211057.GA10800@flint.arm.linux.org.uk> <10f740e80906021418i1d58f5eer940e7a8ec9fb8b9e@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <10f740e80906021418i1d58f5eer940e7a8ec9fb8b9e@mail.gmail.com> Sender: linux-arch-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Geert Uytterhoeven Cc: Grant Likely , James Bottomley , ksummit-2009-discuss@lists.linux-foundation.org, linux-arch@vger.kernel.org, linux-embedded@vger.kernel.org, Josh Boyer , Tim Bird On Tue, Jun 02, 2009 at 11:18:04PM +0200, Geert Uytterhoeven wrote: > > The big problem we have is that the only commonality between differ= ent > > SoCs is that the CPU executes ARM instructions. =A0Everything else = is > > entirely up to the SoC designer - eg location of memory, spacing of > > memory banks, type of interrupt controller, etc is all highly SoC > > specific. =A0Nothing outside of the ARM CPU itself is standardized. >=20 > That sounds very similar to m68k, which does support generic kernels > (except for Sun-3, which uses a completely different MMU)? =46or MIPS we currently have a concept of system families. The user se= lects one in the "System type" Kconfig menu. With few exceptions that are no= t worth considering these system types are incompatible so there are currently 37 families of incompatible platforms with more being added. Ralf