From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e34.co.us.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 2B24EDDEE7 for ; Thu, 12 Jun 2008 03:33:40 +1000 (EST) Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e34.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m5BHXbi5009626 for ; Wed, 11 Jun 2008 13:33:37 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m5BHXaov171638 for ; Wed, 11 Jun 2008 11:33:36 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m5BHXaul030934 for ; Wed, 11 Jun 2008 11:33:36 -0600 Date: Wed, 11 Jun 2008 13:32:47 -0400 From: Josh Boyer To: "Darcy Watkins" Subject: Re: PPC to PowerPC Migration Message-ID: <20080611133247.0ac8b7c6@zod.rchland.ibm.com> In-Reply-To: References: <161B3BAD77161449A144FF054231C3D6022A3E4A@uss-am-xch-01.am.trimblecorp.net> <20080611123254.64fabf64@vader.jdub.homelinux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: vb , Mike Timmons , Andy Schmidt , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 11 Jun 2008 10:15:03 -0700 "Darcy Watkins" wrote: > Hi Josh, > > I think it would be more helpful if I were to tidy it a bit and add AMCC > Taihu boot support to it first. Then submit it. People are more likely > to have access to a Taihu than one of our boards. > > What I mean by "AMCC Taihu boot support" is that the board would come up > just like our Taihushui/Kolsch family of boards, but would not include > the extra drivers, etc needed for USB gadgets, the LCD and other like > items that are on the AMCC board. That sounds like a fine plan. If you'd like, you can submit both at the same time (as separate patches). More board ports are always welcome, particularly for stock eval boards. > Once I get this done, I can submit BSP patch sets for kernel 2.6.25 and > 2.6.26. If there is demand, I could submit a BSP patch set for 2.6.24 > as well. Preferably, you'd submit to the tip of the git tree for 4xx. With the pace of kernel development, releasing patches for "old" kernels just means that someone has to forward port them to the latest tree. That might be a small effort, but in practice it's best to work with bleeding edge if you're going to submit a patch for inclusion. Don't be discouraged by that. There are those that will help you if you run into obstacles. > Please send me (or URL to) summarized patch submission instructions / > guidelines. The easiest place to start is Documentation/SubmittingPatches in the kernel tree. josh