[gulshan.karm...@gmail.com]
>
>
> Hi All,
>
> Can anyone explain why Google chooses odd versions of Kernel
> tree ?
>
>It is valid not to use the latest version for developments but
> why always odd ones like 25 and 27.
2.6.25 was the most recent released kernel when we were fin
Hi All,
Can anyone explain why Google chooses odd versions of Kernel
tree ?
It is valid not to use the latest version for developments but
why always odd ones like 25 and 27.
rgds,
Gulshan
--~--~-~--~~~---~--~~
unsubscribe: android-kernel+unsubscr.
Mark,
Happy new year!
> Cupcake for x86 targets is running 2.6.25, and yet there is a 2.6.27
> > kernel branch in mainline as well.
>
I believe what you meant to say was that the pre-builts for the EeePC 701
target came with a 2.6.25 kernel. There is no inherent requirement placed on
x86 targets
[markgross ]
>
> We have a number of kernel patches for running android on IA targets.
> I'm not sure which branch(es) to have these pushed too.
>
> Cupcake for x86 targets is running 2.6.25, and yet there is a 2.6.27
> kernel branch in mainline as well.
Cupcake *should* be using 2.6.27 everywh
We have a number of kernel patches for running android on IA targets.
I'm not sure which branch(es) to have these pushed too.
Cupcake for x86 targets is running 2.6.25, and yet there is a 2.6.27
kernel branch in mainline as well.
For now lets just consider a simple patch that touches alarm.c to
