From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nommos.sslcatacombnetworking.com (nommos.sslcatacombnetworking.com [67.18.224.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id BEC1067A06 for ; Wed, 26 Apr 2006 04:31:28 +1000 (EST) In-Reply-To: <20060425182418.GA1132@gate.ebshome.net> References: <4C61B597-BD91-4D05-BB40-43DE0319F123@kernel.crashing.org> <17017F03-078C-4B7F-A961-EC371F534E27@embeddedalley.com> <34C11E8A-ED04-490F-B601-841DC1F94AD6@kernel.crashing.org> <20060425074902.GA20228@gate.ebshome.net> <66B13296-80E8-4C9E-803D-F4E3D7AABB25@embeddedalley.com> <853005AF-8F43-454D-80E6-F39308F89A47@kernel.crashing.org> <20060425170857.GE20228@gate.ebshome.net> <20060425180119.GF20228@gate.ebshome.net> <265F73F8-F641-4EDD-B88F-A2B2F7FA1308@kernel.crashing.org> <20060425182418.GA1132@gate.ebshome.net> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Kumar Gala Subject: Re: 85xx FDT updates? Date: Tue, 25 Apr 2006 13:31:21 -0500 To: Eugene Surovegin Cc: "linuxppc-dev@ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Apr 25, 2006, at 1:24 PM, Eugene Surovegin wrote: > On Tue, Apr 25, 2006 at 01:14:55PM -0500, Kumar Gala wrote: >> >>> What you will end up with is that that small amount of embedded >>> people >>> who bother to contribute something back will stop doing this. We are >>> more than capable of maintaining our internal kernel trees :). >> >> I'm not sure what to say to this. Things need to move forward at >> some point. > > I don't see how removing features and breaking compatibility with > almost _all_ current embedded PPC boards boards is "moving forward". > Enlighten me, please. I'm not talking about all embedded PPC boards. I'm taking about the subset that exists for 85xx. Also, its moving forward as the standard way of booting future systems. >> I still not clear as to what exactly you are advocating >> beyond that we should keep the arch/ppc code around for ever. > > Providing compatibility for non-flat-tree firmware. This doesn't mean > keeping arch/ppc. And how do you suggest we do this? My argument is for the boards I'm talking about updating u-boot is the easiest and most straight forward solution. I'm not advocating this at the right solution for all boards. - kumar