List Archive: gentoo-ppc-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Do these kernels have Xilinx V2P (Virtex-II Pro) support?
I can add it.
Pieter Van den Abeele wrote:
> This is what we are working on regarding ppc kernels:
> *From: *Pieter Van den Abeele <firstname.lastname@example.org>
> *Date: *Tue 27 Apr 2004 16:32:29 CEST
> *To: *email@example.com
> *Cc: *Pieter Van den Abeele <firstname.lastname@example.org>, email@example.com
> *Subject: PPC kernel plan
> 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)
> - 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.
> - 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
> Preferably use linux-headers.
firstname.lastname@example.org mailing list