On Mon, Feb 9, 2009 at 1:31 AM, Nimit Manglick <nimitandr...@gmail.com> wrote: > Thanx Mathias. > > is there any document which explains the graphical architecture / design of > android.?
Unfortunately no. There will be one once the new architecture is in place. > I mean complete flow from Application till the kernel obviously OpenGl in > between. ? > > I have struggled with it a lot but still the complete picture is not yet > clear to me :( Mathias > > Regards > Nimit > > On Mon, Feb 9, 2009 at 2:33 PM, Mathias Agopian <pixelflin...@google.com> > wrote: >> >> On Mon, Feb 9, 2009 at 12:59 AM, Nimit Manglick <nimitandr...@gmail.com> >> wrote: >> > One more point. >> > >> > If somehow i made it work now by tweaking here and there in android, >> > >> > will this work of mine become obsolete with future releases of android >> > ?? >> >> Most definitely yes. >> >> > or android wil be going to maintain its backward compatibilty even it >> > releases with HAL ? >> >> No, android doesn't maintain any form of backward compatibility with >> non public APIs and HAL modules. >> >> Mathias >> >> >> > On Mon, Feb 9, 2009 at 1:43 PM, Nimit Manglick <nimitandr...@gmail.com> >> > wrote: >> >> >> >> ok.. >> >> >> >> So can you give me a brief idea what all components / layers / >> >> framework >> >> needs to modify >> >> >> >> in android to support h/w acceleration (If i think to modify). >> >> >> >> On Mon, Feb 9, 2009 at 1:12 PM, Mathias Agopian >> >> <pixelflin...@google.com> >> >> wrote: >> >>> >> >>> On Sun, Feb 8, 2009 at 11:21 PM, Nimit Manglick >> >>> <nimitandr...@gmail.com> >> >>> wrote: >> >>> > Hi Mathias, >> >>> > >> >>> > Thanx for the quick response. >> >>> > >> >>> > So bottom line is :- >> >>> > >> >>> > Currently android cant use hardware acceleration of any other >> >>> > hardware >> >>> > other >> >>> > than G1. >> >>> > Is it ?? >> >>> >> >>> Not without a lot of pain, and actually modifying several elements of >> >>> the framework. >> >>> >> >>> > And work is going on to make it portable just like any other >> >>> > component >> >>> > like >> >>> > its HAL interface ?? Right ?? >> >>> >> >>> Correct. >> >>> >> >>> > If yes then when can such code be availbale to open source ? >> >>> >> >>> That's one of my top priority, unfortunately I don't know when it'll >> >>> be ready. "As soon as possible" is the best answer I can give. >> >>> >> >>> Mathias >> >>> >> >>> >> >>> > Thanks & Regards >> >>> > Nimit >> >>> > >> >>> > >> >>> > On Mon, Feb 9, 2009 at 12:08 PM, Mathias Agopian >> >>> > <pixelflin...@google.com> >> >>> > wrote: >> >>> >> >> >>> >> Android is not ready at the moment to work with a different GPU >> >>> >> than >> >>> >> that of the G1. We're working on it :-) >> >>> >> >> >>> >> Mathias >> >>> >> >> >>> >> >> >>> >> On Sun, Feb 8, 2009 at 10:31 PM, Nimit Manglick >> >>> >> <nimitandr...@gmail.com> >> >>> >> wrote: >> >>> >> > Hi, >> >>> >> > >> >>> >> > I have my android working on 2.6.24 kernel on TI Omap 3530 EVM, >> >>> >> > now >> >>> >> > i >> >>> >> > want >> >>> >> > to >> >>> >> > >> >>> >> > enable hardware acceleration onto it. >> >>> >> > >> >>> >> > As this is a very old post (more than 2 months old) , so what are >> >>> >> > the >> >>> >> > current steps / way >> >>> >> > >> >>> >> > to enable hardware acceleration onto my omap 3530. >> >>> >> > >> >>> >> > As i understood from this post that my vendor (TI here) has to >> >>> >> > provide >> >>> >> > me >> >>> >> > the >> >>> >> > >> >>> >> > hardware implementation of OpenGL as libhgl.so and the driver , >> >>> >> > other >> >>> >> > than >> >>> >> > this what all i need to do ?? >> >>> >> > >> >>> >> > Thanks & Regards >> >>> >> > Nimit >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > On Wed, Nov 26, 2008 at 9:49 PM, Dave Sparks >> >>> >> > <davidspa...@android.com> >> >>> >> > wrote: >> >>> >> >> >> >>> >> >> You have two choices for taking advantage of your h/w >> >>> >> >> acceleration: >> >>> >> >> >> >>> >> >> 1. Integrate your codecs into the OpenCore framework. You can do >> >>> >> >> this >> >>> >> >> using the exising OpenMax decoder node, or you can adapt one of >> >>> >> >> PV's >> >>> >> >> native decoder nodes to work with your hardware. >> >>> >> >> >> >>> >> >> 2. Implement your own media player (MediaPlayerInterface.h). If >> >>> >> >> your >> >>> >> >> hardware vendor already has hardware codecs integrated into >> >>> >> >> another >> >>> >> >> media framework (e.g. gstreamer), you could write an adapter >> >>> >> >> class >> >>> >> >> that sits on top of the media framework. >> >>> >> >> >> >>> >> >> On Nov 26, 2:20 am, Pivotian <sujit2...@gmail.com> wrote: >> >>> >> >> > sorry Mathias for repeating my question but every time I put >> >>> >> >> > this >> >>> >> >> > question, its overridden by some other questions and it didn't >> >>> >> >> > got >> >>> >> >> > your attention. I have some doubt regarding video codecs: >> >>> >> >> > >> >>> >> >> > I suppose that Android uses the OPENCORE from packet video to >> >>> >> >> > do >> >>> >> >> > all >> >>> >> >> > the stuffs related to video encoding and decoding. I want to >> >>> >> >> > use >> >>> >> >> > the >> >>> >> >> > built in capabilities of my processor which provides Standard >> >>> >> >> > level >> >>> >> >> > encoding/decoding of multiple content formats including MPEG4, >> >>> >> >> > H.263, >> >>> >> >> > H.264. How i will use the inbuilt hardware based encoding >> >>> >> >> > decoding >> >>> >> >> > instead of Android's software based opencore ? >> >>> >> >> >> >>> >> > >> >>> >> > >> >>> >> > > >> >>> >> > >> >>> >> >> >>> >> >> >>> > >> >>> > >> >>> > > >> >>> > >> >>> >> >>> >> >> >> > >> > >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
