[gentoo-ppc-dev] Fwd: PPC kernel plan

[gentoo-ppc-dev] Fwd: PPC kernel plan

[Pieter Van den Abeele]

[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]

This is what we are working on regarding ppc kernels:

> From: Pieter Van den Abeele <pvdabeel@gentoo.org>
> Date: Tue 27 Apr 2004 16:32:29 CEST
> To: ppc@gentoo.org
> Cc: Pieter Van den Abeele <pvdabeel@gentoo.org>, 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.

[-- Attachment #2: Type: text/enriched, Size: 2471 bytes --]

<fontfamily><param>Arial</param><color><param>0000,0000,0000</param><x-tad-bigger>This
is what we are working on regarding ppc kernels:</x-tad-bigger></color>

</fontfamily>

<excerpt><bold><color><param>0000,0000,0000</param><x-tad-bigger>From:
</x-tad-bigger></color></bold><x-tad-bigger>Pieter Van den Abeele
<<pvdabeel@gentoo.org>

</x-tad-bigger><bold><color><param>0000,0000,0000</param><x-tad-bigger>Date:
</x-tad-bigger></color></bold><x-tad-bigger>Tue 27 Apr 2004 16:32:29
CEST

</x-tad-bigger><bold><color><param>0000,0000,0000</param><x-tad-bigger>To:
</x-tad-bigger></color></bold><x-tad-bigger>ppc@gentoo.org

</x-tad-bigger><bold><color><param>0000,0000,0000</param><x-tad-bigger>Cc:
</x-tad-bigger></color></bold><x-tad-bigger>Pieter Van den Abeele
<<pvdabeel@gentoo.org>, johnm@gentoo.org

</x-tad-bigger><bold><color><param>0000,0000,0000</param><x-tad-bigger>Subject:
</x-tad-bigger></color><x-tad-bigger>PPC kernel plan

</x-tad-bigger></bold>

Hi,


I would like to make the following proposal regarding ppc kernels:



<bold>Ebuild categories:</bold>


- 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)



<bold>Virtuals:</bold>


- 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.


<bold>Notes:</bold>


- 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



<bold>Headers:</bold>


Preferably use linux-headers.

</excerpt>

Re: [gentoo-ppc-dev] Fwd: PPC kernel plan

[Mike Wellington]

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 <pvdabeel@gentoo.org>
>     *Date: *Tue 27 Apr 2004 16:32:29 CEST
>     *To: *ppc@gentoo.org
>     *Cc: *Pieter Van den Abeele <pvdabeel@gentoo.org>, 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

Re: [gentoo-ppc-dev] Fwd: PPC kernel plan

[David Holm <dholm@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
where can I find the patches?

//David Holm

On Friday 07 May 2004 15.47, Mike Wellington wrote:
> 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 <pvdabeel@gentoo.org>
> >     *Date: *Tue 27 Apr 2004 16:32:29 CEST
> >     *To: *ppc@gentoo.org
> >     *Cc: *Pieter Van den Abeele <pvdabeel@gentoo.org>, 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAm5jNxVDe1wIoqX0RAkkwAJsGOKowvbrT+LV25p1MnLzIi03B5QCgpT02
5JKfCjsXDQTOTnGv4YXtGfc=
=+auq
-----END PGP SIGNATURE-----

--
gentoo-ppc-dev@gentoo.org mailing list