[oe] [RFC] handhelds-pxa-2.6 -> linux-handhelds-2.6

Erik Hovland erik at hovland.org
Sat Oct 14 15:35:21 UTC 2006


On Sat, Oct 14, 2006 at 05:17:36PM +0200, pHilipp Zabel wrote:
> On 10/14/06, Erik Hovland <erik at hovland.org> wrote:
> > On Sat, Oct 14, 2006 at 04:23:00PM +0300, Paul Sokolovsky wrote:
> > > > On Fri, Oct 13, 2006 at 07:51:07PM +0300, Paul Sokolovsky wrote:
> > > >> 2. "pxa" there is misleading, as 2.6 tree supports different
> > > >> architectures. Handhelds.org tree as of now supports PXA, SA, and S3
> > > >> (Samsung) devices. To the various degrees, but that's improving.
> > >
> > > > Technically, the pxa is not misleading per se. That recipe only builds a
> > > > kernel for pxa devices.
> > >
> > >   Well that's why I brought this to discussion. By "only builds" do
> > > you mean the current state of affairs or some inherent constraint on
> > > that recipe?
> >
> > An inherent constraint of the recipe is that it will build a kernel
> > which will only run on h3900 and h5400, which are pxa devices, h3600
> > cannot run a kernel built with the recipe. That is traditionally why we
> > named the recipes -pxa and -sa.
> 
> How is this an inherent constraint? Looking at a diff between
> handhelds-pxa-2.6_cvs.bb and handhelds-sa-2.6_cvs.bb I don't see
> anything architecture specific?

Well, *ahem* the defconfig that the -sa bb specifies will build a sa
kernel, the defconfig that -pxa specifies will build a pxa kernel.

The recipes themselves do not bild in the constraint. Thanks for double
checking.

E

-- 
Erik Hovland
mail: erik at hovland.org
web: http://hovland.org/
PGP/GPG public key available on request




More information about the Openembedded-devel mailing list