Thanks for your comment.
It will be a big help for me.

2009/4/9, Michael Trimarchi <[email protected]>:
>
> [email protected] wrote:
>> Thanks for your response.
>> One more question,
>>
>>
>>> Hoegaarden wrote:
>>>
>>>> When wil the 2.6.29 android kernel be available on your repo server?
>>>>
>>>> 2009/4/9, Mike Chan [email protected]>:
>>>>
>>>>> We are in the progress of re-basing to 2.6.29. I'd suggest sticking
>>>>> with 2.6.27 unless you're feeling quite adventurous.
>>>>>
>>>>> On Tue, Mar 17, 2009 at 1:28 AM, Jackie Wu <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I just found some logs in Android kernel project about kernel 2.6.29,
>>>>>> like "Fix 2.6.29 build".
>>>>>> Is the Android kernel upgraded to 2.6.29? Where can I get it?
>>>>>>
>>>>>> Thanks
>>>>>> Weihua Wu
>>>>>>
>>> On openmoko project we use 2.6.29 with android without any problem,
>>> simple change
>>> in the wakelock path. I provide a patch against the kernel that put all
>>> the android stuff
>>> under the driver/staging/android directory
>>>
>>> Michael
>>>
>>
>> Can we get the 2.6.29 kernel source with android from somewhere?
>> Or Is the android support already contained in vanilla kernel 2.6.29 ?
>>
>> I know that some part of the android drivers are stored in the vanilla
>> kernel 2.6.29,
>> on the locaton "drivers/staging/android" , but according to the simple
>> look of
>>
> I add the console support too, and apply a patch in the power part.
>> the source code I think those are not enough to run the android , for
>> example,
>> I could not find the ashmem implementation.
>>
> Yes in the openmoko we have the ashmem patch too. That was done by Sean
> McNeil before.
> I run a prestage of the cupcake too. In latest sync to android I have
> the fix build merge
> to 2.6.29. For me the best approch is just use the minimal requirement
> on the latest kernel
> Michael
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel
-~----------~----~----~----~------~----~------~--~---

Reply via email to