From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 6B2AC67A77 for ; Thu, 20 Jan 2005 10:23:48 +1100 (EST) From: Benjamin Herrenschmidt To: David Woodhouse In-Reply-To: <1106120622.10851.42.camel@baythorne.infradead.org> References: <200501082324.j08NOIva030415@hera.kernel.org> <20050109151353.GA9508@suse.de> <1105956993.26551.327.camel@hades.cambridge.redhat.com> <1106107876.4534.163.camel@gaston> <1106120622.10851.42.camel@baythorne.infradead.org> Content-Type: text/plain Date: Thu, 20 Jan 2005 10:22:18 +1100 Message-Id: <1106176939.5294.39.camel@gaston> Mime-Version: 1.0 Cc: linuxppc-dev list , Linus Torvalds , "H. Peter Anvin" , Linux Kernel list Subject: Re: [PATCH] raid6: altivec support List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2005-01-19 at 07:43 +0000, David Woodhouse wrote: > On Wed, 2005-01-19 at 15:11 +1100, Benjamin Herrenschmidt wrote: > > We should probably "backport" that simplification to ppc32... > > Yeah.... I'm increasingly tempted to merge ppc32/ppc64 into one arch > like mips/parisc/s390. Or would that get vetoed on the basis that we > don't have all that horrid non-OF platform support in ppc64 yet, and > we're still kidding ourselves that all those embedded vendors will > either not notice ppc64 or will use OF? Oh well... i've though about it too, and decided that I was not ready to try it. For one, the problem you mention, with the pile of embedded junk. I made the design decision to define an OF client interface as the standard & mandatory entry mecanism to the ppc64 kernel (except legacy iSeries of course, but I don't want that to multiply). That or the kexec-like entrypoint passing a flattened device-tree in. Also, there are other significant differences in other areas. At this point, I think the differences are bigger than the common code. What would be interesting would be to proceed incrementally, having a directory somewhere to put the "common" ppc/ppc64 code, and slowly moving things there. Ben.