Hi all
does anyone port android to 18bpp mode only LCD based platform?

On 09/29/09 07:46 PM, android-porting group wrote:
>  
> android-porting
> http://groups.google.com/group/android-porting?hl=en
>
> [email protected]
>
> Today's topics:
>
> * Got stuck when booting - 1 messages, 1 author
>  http://groups.google.com/group/android-porting/t/299cdc69348279ff?hl=en
> * Dalvik virtual machine build on x86 - 4 messages, 2 authors
>  http://groups.google.com/group/android-porting/t/41518ff5f1b97a3b?hl=en
> * MediaFramework Test material - 1 messages, 1 author
>  http://groups.google.com/group/android-porting/t/684744d62da19b2b?hl=en
> * mp4 composer api - 1 messages, 1 author
>  http://groups.google.com/group/android-porting/t/b849610f194f4103?hl=en
> * debugging parcel.cpp file - 1 messages, 1 author
>  http://groups.google.com/group/android-porting/t/77e1c13cd9ef1bb2?hl=en
>
> ==============================================================================
> TOPIC: Got stuck when booting
> http://groups.google.com/group/android-porting/t/299cdc69348279ff?hl=en
> ==============================================================================
>
> == 1 of 1 ==
> Date: Tues, Sep 29 2009 2:25 am 
> From: Kiki  
>
>
> Hi All,
>
>    Good news!I can boot the emulator now.
> I add several logs to linker.c, and the output info surprised me.
> All these 3 so size are bigger than built lib size more than 50%!
> That is to say, "libavcodec.so" under /out/target/product/generic/
> obj/
> lib is 2M,
> but you can see its real size is more than 6M when running!
> I gave the libavcodec.so a slot in "prelink-linux-arm.map" with the
> size of 3M only, so it got stuck when booting-_-//
> When I changed the slot size to 7M, booting successfully!
> I hope this case can help other people.
>
>
> Nevertheless, who can tell me why the lib size became so large when
> running?
>
>
> 09-29 04:14:23.993: DEBUG/Linker(554): mmap prelinked lib
> libavutil.so
> at 0x33800000, size = 45056
> 09-29 04:14:23.993: DEBUG/Linker(554): libavutil.so is mapped to
> 0x33800000
> 09-29 04:14:23.993: DEBUG/Linker(554): mmap prelinked lib
> libavcodec.so at 0x33100000, size = 6950912
> 09-29 04:14:23.993: DEBUG/Linker(554): libavcodec.so is mapped to
> 0x33100000
> 09-29 04:14:24.162: DEBUG/Linker(554): mmap prelinked lib
> libavformat.so at 0x33000000, size = 737280
> 09-29 04:14:24.162: DEBUG/Linker(554): libavformat.so is mapped to
> 0x33000000
>
>
>
>
>
> ==============================================================================
> TOPIC: Dalvik virtual machine build on x86
> http://groups.google.com/group/android-porting/t/41518ff5f1b97a3b?hl=en
> ==============================================================================
>
> == 1 of 4 ==
> Date: Tues, Sep 29 2009 2:38 am 
> From: Rakesh Kumar  
>
>
> Hi All,
>           I want to build Dalvik on x86 platform. Please tell me the
> procedure to build Dalvik for x86 and run it.
>           How can I use the scripts present at this link
> http://code.google.com/p/dvk
>
> Regards
> Rakesh
>
>
>
>
> == 2 of 4 ==
> Date: Tues, Sep 29 2009 2:43 am 
> From: Avtar Singh  
>
>
> How to build: http://code.google.com/p/dvk/wiki/Installing
> How to run inside a virtual machine:
> http://groups.google.com/group/android-porting/msg/32b3709b4ae4f1d5
>
> Are you not able to build / getting any errors while building?
>
>
> On Tue, Sep 29, 2009 at 3:08 PM, Rakesh Kumar <[email protected]> wrote:
>
>   
>> Hi All,
>>           I want to build Dalvik on x86 platform. Please tell me the
>> procedure to build Dalvik for x86 and run it.
>>           How can I use the scripts present at this link
>> http://code.google.com/p/dvk
>>
>> Regards
>> Rakesh
>>
>>     
>
>
>
>
> == 3 of 4 ==
> Date: Tues, Sep 29 2009 3:35 am 
> From: Avtar Singh  
>
>
> It is the "idvk" file you see in the folder where you have extracted
> idvk.tar. Typing ./idvk instead of ./idvk.sh will do fine:
>
> ./idvk get
> ./idvk build x86
>
>
> On Tue, Sep 29, 2009 at 3:24 PM, Rakesh Kumar <[email protected]> wrote:
>
>   
>> I am sorry but I am not able to find any idvk.sh file.
>>
>> Rakesh
>>
>>
>> On Tue, Sep 29, 2009 at 3:08 PM, Rakesh Kumar <[email protected]>wrote:
>>
>>     
>>> Hi All,
>>>           I want to build Dalvik on x86 platform. Please tell me the
>>> procedure to build Dalvik for x86 and run it.
>>>           How can I use the scripts present at this link
>>> http://code.google.com/p/dvk
>>>
>>> Regards
>>> Rakesh
>>>
>>>       
>>     
>
>
>
>
> == 4 of 4 ==
> Date: Tues, Sep 29 2009 3:44 am 
> From: Rakesh Kumar  
>
>
> Thank you very much for your great help.
>
>
> Rakesh
>
> On Tue, Sep 29, 2009 at 4:05 PM, Avtar Singh <[email protected]> wrote:
>
>   
>> It is the "idvk" file you see in the folder where you have extracted
>> idvk.tar. Typing ./idvk instead of ./idvk.sh will do fine:
>>
>> ./idvk get
>> ./idvk build x86
>>
>>
>>
>> On Tue, Sep 29, 2009 at 3:24 PM, Rakesh Kumar <[email protected]>wrote:
>>
>>     
>>> I am sorry but I am not able to find any idvk.sh file.
>>>
>>> Rakesh
>>>
>>>
>>> On Tue, Sep 29, 2009 at 3:08 PM, Rakesh Kumar <[email protected]>wrote:
>>>
>>>       
>>>> Hi All,
>>>>           I want to build Dalvik on x86 platform. Please tell me the
>>>> procedure to build Dalvik for x86 and run it.
>>>>           How can I use the scripts present at this link
>>>> http://code.google.com/p/dvk
>>>>
>>>> Regards
>>>> Rakesh
>>>>
>>>>         
>>>       
>
>
>
>
>
> ==============================================================================
> TOPIC: MediaFramework Test material
> http://groups.google.com/group/android-porting/t/684744d62da19b2b?hl=en
> ==============================================================================
>
> == 1 of 1 ==
> Date: Tues, Sep 29 2009 4:11 am 
> From: Guildazz  
>
>
> Thank you guys,
> I'll use my own files for the time being.
> Please let us know when/if your internal test files are made public.
>
>
>
>
>
>
>
> ==============================================================================
> TOPIC: mp4 composer api
> http://groups.google.com/group/android-porting/t/b849610f194f4103?hl=en
> ==============================================================================
>
> == 1 of 1 ==
> Date: Tues, Sep 29 2009 4:15 am 
> From: bitandroid  
>
>
> Hi All,
> I have raw encoded frames and i want to put them into a mp4 file.Do we
> have api for composing mp4 ??
>
>
>
>
> ==============================================================================
> TOPIC: debugging parcel.cpp file
> http://groups.google.com/group/android-porting/t/77e1c13cd9ef1bb2?hl=en
> ==============================================================================
>
> == 1 of 1 ==
> Date: Tues, Sep 29 2009 4:27 am 
> From: Dhananjay Joshi  
>
>
> On Mon, Sep 28, 2009 at 11:07 PM, Dianne Hackborn <[email protected]>wrote:
>
>   
>> Parcel I am pretty sure already has a bunch of log lines in it that you can
>> turn on.  If you need more, add them.  Of course the first thing you want to
>> do is get the stack crawl where it is crashing to start focusing your
>> effort.
>>
>> On Sun, Sep 27, 2009 at 11:30 PM, dhananjay 
>> <[email protected]>wrote:
>>
>>     
>>> Hi All,
>>>           i'm trying to port android on my big endian platform , and
>>> m getting issues in IPC communication bider . object written by one
>>> procees coudnt be read by another process it is coming null at the
>>> other side , but to debug this problem if i put print in parcel.cpp
>>> whole system
>>> is crashing , so i cant put print in binder or parcel file. does
>>> anybody know how to get info logs from threse two file.???????
>>> also the data written in parcel follows host system' s endian order ,
>>> as i compiled my source code on x86 system ,where  Byte order is
>>> little endian so anybody having any idea where to specify correct byte
>>> order in order to have IPC running on my big endian system.
>>>
>>> Regards,
>>> Dhananjay
>>>
>>>
>>>       
>> --
>> Dianne Hackborn
>> Android framework engineer
>> [email protected]
>>
>> Note: please don't send private questions to me, as I don't have time to
>> provide private support, and so won't reply to such e-mails.  All such
>> questions should be posted on public forums, where I and others can see and
>> answer them.
>>
>>
>>
>>     
>> Hi Dianne
>>     
>                 thanks for replying.....
> yeah .it was my mistake ..prints are coming from Parcel.cpp , further
> debugging yields that
> in ViewRoot.java file request for window service is resulting in openSession
> Object  ,which is
> further having IPC commn and after readStrongBinder() in
> IWindowManager.java(generated file) openSession is returning NULL.so my
> point is from the client  side i have tracked writeStrongBinder() in switch
> case which is not NULL only the reply is coming NULL,
> and this is happening only for windoesession not  for InputMethodManager
> which i tracked from logs , requesting the  IPC service and getting the one.
> and for remoteobject .for localobjecct IPC seems to be working fine.so i
> want to track code from server side which is actually writting in to kernel
> driver , so that i can get insight of what is happening from read and write
> from kernel driver which file i should look?
>  or is there any other way to track this? please reply....
>
> Regards,
> DJ
>
>
>
>
> ==============================================================================
>
> You received this message because you are subscribed to the Google Groups 
> "android-porting"
> group.
>
> To post to this group, send email to [email protected] or visit
> http://groups.google.com/group/android-porting?hl=en
>
> To unsubscribe from this group, send email to 
> [email protected]
>
> To change the way you get mail from this group, visit:
> http://groups.google.com/group/android-porting/subscribe?hl=en
>
> To report abuse, send email explaining the problem to [email protected]
>
> ==============================================================================
> Google Groups: http://groups.google.com/?hl=en
>
>   


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

Reply via email to