From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1898 invoked from network); 7 May 2004 13:48:44 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 7 May 2004 13:48:44 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BM5iW-0005m0-Ge for arch-gentoo-ppc-dev@lists.gentoo.org; Fri, 07 May 2004 13:48:44 +0000 Received: (qmail 5024 invoked by uid 50004); 7 May 2004 13:48:44 +0000 Mailing-List: contact gentoo-ppc-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-ppc-dev@gentoo.org Received: (qmail 16914 invoked from network); 7 May 2004 13:48:43 +0000 Message-ID: <409B938A.3070607@lucent.com> Date: Fri, 07 May 2004 07:47:54 -0600 From: Mike Wellington User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pieter Van den Abeele CC: gentoo-ppc-dev@lists.gentoo.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean Subject: Re: [gentoo-ppc-dev] Fwd: PPC kernel plan X-Archives-Salt: 0689f29b-0766-4778-8a60-fa0746bc055b X-Archives-Hash: 461ce494430104058845a70faf13ca51 Do these kernels have Xilinx V2P (Virtex-II Pro) support? I can add it. -mike wellington mike@bithead.com Pieter Van den Abeele wrote: > This is what we are working on regarding ppc kernels: > > *From: *Pieter Van den Abeele > *Date: *Tue 27 Apr 2004 16:32:29 CEST > *To: *ppc@gentoo.org > *Cc: *Pieter Van den Abeele , johnm@gentoo.org > *Subject: PPC kernel plan > * > Hi, > > I would like to make the following proposal regarding ppc kernels: > > > *Ebuild categories:* > > - development-sources: 2.6 > > - gentoo-sources: 2.4 + whateverwewant > - gentoo-dev-sources: 2.6 + whateverwewant + gcloop > > - benh-sources: 2.4 + benh > - benh-dev-sources: 2.6 + benh + gcloop > > - pegasos-sources: 2.4 + pegasos > - pegasos-dev-sources: 2.6 + pegasos + gcloop > > - ames-dev-sources: 2.6 + ames (+ gcloop) > > > *Virtuals:* > > - virtual/ppc-sources -> benh-sources || pegasos-sources > - virtual/ppc-dev-sources -> benh-dev-sources || pegasos-dev-sources > || gentoo-dev-sources || development-sources > > - virtual/ppc64-sources -> ames-dev-sources > - virtual/ppc64-dev-sources -> ames-dev-sources > > The idea for having 'dev' and 'regular' sources i to prevent portage > from upgrading users with a 2.4 kernel to a 2.6 kernel. > Relation to keywording: dev-sources can be masked stable, no need to > keep those in unstable forever. > > The idea for separating pegasos from benh is to make keywording easier. > > *Notes:* > > - ppc-sources-crypto has no maintainer and has been removed from cvs > - ppc-sources-dev merges into gentoo-sources on the condition that > gentoo-sources migrates *completely* to kernel-2.eclass > - ppc-sources-benh gets merged with ppc-sources and the set is > renamed to benh-sources > - pegasos compatible ebuilds go into pegasos-* > - ppc-development-sources is renamed to benh-dev-sources > > > *Headers:* > > Preferably use linux-headers. > -- gentoo-ppc-dev@gentoo.org mailing list