You can't.
And why would you want to do such a thing, 2.6.24 is a few years old now,
right? Using older kernel versions like that is not a good thing to do.
good luck,
greg k-h
Very old. Hundreds of thousands of kernel changes old. Do you really realize
how old it is?
> but that's the latest we have.
Who is "we" here? Why can't you use a newer kernel version? What is keeping
you from updating? Out-of-tree kernel drivers? If so, where are they, I will
be glad to forward port them for you and get them into the main kernel tree.
> Is there a way around?
As this seems to be a self-inflicted requirement, it seems that you would be
the only one to be able to resolve this. You can't ask the community to do
backporting work for you.
> We have our patches to be taken care of
Where are these patches?
> so what is the best way to get Android specific patches form the source,
> which version of linux kernel should I diff it with for getting patches?
Just do a diff on the git tree, it makes it very trivial to do so.
good luck,
greg k-h
That is because it is based off of the upstream kernel.org tree. It
also has 2.6.13 in the tree to, that doesn't mean android works on it :)
> So if I am correct I have two options-
> (i) Use the android 2.6.24 kernel and download other platform related
> code from the git and see if it builds, this is certainly hopeless I
> feel, or
It would require a lot of backporting of code, a non-trivial ammount of
work.
> (ii) Use the latest stable release of Android and port our changes to
> that kernel. This is feasible but very time consuming I think.
No, not at all, that is what you should do, as it will provide you a
path for the future. What happens when android moves to 2.6.29?
2.6.32? Will you continue to backport to an old, unsupported, buggy,
and insecure kernel version like 2.6.24? I hope not.
> Let me know if what I have deduced is correct. Does it mean that one
> cannot download Android sources for some specific kernel version like
> 2.6.24 or 2.6.27 or 2.6.29? Wouldn't it have been very useful if it
> was possible?
No, many tens of thousands of changes have gone on between those kernel
versions, it is better for you to get your changes into the main kernel
tree, or upgrade yourself.
Again, if you need help forward porting your kernel changes to the
latest kernel and getting the code into the tree, please let me know, we
can do that work.
Also, what specifically is keeping you at the 2.6.24 kernel release?
What changes have you made that requires such an old and obsolete
kernel?
thanks,
greg k-h
Yes, it is easy if you know what changes are needed to be done :)
Why not port to .29 instead of the obsolete .27 kernel?
> I want to know what are the architectural changes in 2.6.24 and 2.6.27
> which could affect the drivers.
>
> How difficult could it be for porting these drivers
> audio,video,usb,mmc from 24 kernel to 27.
There have been tens of thousands of kernel changes between those two
versions. Do you have a pointer to your drivers to see how much work this
would entail?
Why are the drivers not already in the main kernel source tree? If they were,
they would have been automatically ported for you.
thanks,
greg k-h