I like Mark's approach and here's why:
Device vendors, by Android Licensing, must release their source code.
They do not however have to provide updates for any particular device.
When a new Android comes out a device vendor may simply decide to not port
it to an 'old device' yet rather
port it to
Thanks Dianne,
That is really excellent insider's tip we need to know about.
I will now be using v.2.6.32 for FPGA's linux distribution
On Oct 4, 12:07 pm, Arindam Roy wrote:
> Also Diane, I think it wouldn't be a good idea, not to use the same kernel
> as the android git, as that undoes the ef
Also Diane, I think it wouldn't be a good idea, not to use the same kernel
as the android git, as that undoes the effort that your team has spent, and
leads to duplication.
Another point is, if one is using the same kernel, and reports any issue to
this list, then all the others can easily help. Ot
Here's a story illustrating why I would recommend sticking with the same
version of the kernel that a particular version of Android was developed
against (at least initially).
Froyo was developed against 2.6.32. We are currently developing against
2.6.35 post-Froyo.
I and many others have just g
Yes, thanks for the tip.
On Fri, Sep 24, 2010 at 11:25 PM, Teck Choon Giam
wrote:
> Hi,
>
> On Sat, Sep 25, 2010 at 3:24 AM, hedwin wrote:
>> Some time back I was looking at froyo and what I could find on
>> android.git.kernel.org suggested it might be using kernel version .35
>> while others w
Hi,
On Sat, Sep 25, 2010 at 3:24 AM, hedwin wrote:
> Some time back I was looking at froyo and what I could find on
> android.git.kernel.org suggested it might be using kernel version .35
> while others were using kernel version .32
> So how to know what kernel version to use for which android ve
Some time back I was looking at froyo and what I could find on
android.git.kernel.org suggested it might be using kernel version .35
while others were using kernel version .32
So how to know what kernel version to use for which android version?
On Fri, Sep 24, 2010 at 12:48 AM, Dianne Hackborn wr
We develop each version of Android against a specific version of the kernel,
and make little to no attempt to see if it works on earlier versions of the
kernel. It seems like more often than not if we try to run a newer version
of the platform with the kernel from a previous version that there is
Glibc has a dependency on the 2.6 kenrel tree too, but that doesn't
mean there is a dependency between on 2.6 kernel and another for
propper user mode support.
Yes I have seen those files. They define the sys call ABI that bionic
uses. There is nothing magic or tightly coupled to the specific
ke
hi Mark
Why do you say there is no relationship between userspace and the
kernel version?
Did you check:
Kernel:
include/linux/
and
Android 2.2:
bionic/libc/kernel/common/linux/.
There are same header files shared between kernel and the filesystem.
thus introducing a dependency between
A noobish question kernel gurus:
1. How do I cherry pick the Froyo changes other than the kernel using
repo, for if I use the standard repo command, it syncs up everything
in the latest release.
2. In repo, how do I list down all the projects in a manifest file,
the output of which I can use in rep
What I understood is that bionic needs to be in sync with the kernel.
But getting bionic in sync is a lengthy process.
It feels easier to use git to cherrypick the google specific changes
to a newer kernel version. This is how I do it now.
But it would still be helpfull if the google guys/girls jus
I am booting Froyo (and Eclair) on a 2.6.31 and 2.6.34 kernels today,
I would bet money you could boot them on a 2.6.29 kernel as well.
You just need the critical kenrel patches for it to work. i.e.
binder, asmem, wakelocks, logger, and one or two more, you can easily
rebase out of the refrence k
I keep getting asked about kernel versions and android releases at
work too.
I keep telling people that the only kernel requirements any version of
Android has are that its a 2.6 kernel (for bionic) and it has a small
set of patches (binder, logger, wakelocks, ashmem, and perhaps a few
others that
14 matches
Mail list logo
