Hi, normally these things are provided by your chipset vendor. In case you need to write it from scratch there are sample implementations of gralloc and hwc modules in AOSP.
The display will be up without the hardware composer, but you won't benefit from the Android triple buffering or HW overlays since the VSYNC will be emulated by SW. //Zoltan On Thursday, January 2, 2014 6:59:28 AM UTC+1, [email protected] wrote: > > Hi all, > > I am porting android jelly bean to a new device. I am have ported android > kernel stuffs into my linux kerne by using the patches from android kernel > from their source code. > > I have also added the device(very basic stuffs not wifi etc) files. > > Now I am supposed to add display to my device. I am not concerned about > hardware acceleration in the initial steps. I just want the display. > So I am supposed to add android display HAL. I am confused with three > things. > 1) HWcomposer HAL. > 2) Gralloc. > 3) Framebuffer. > > The confusion that I am running through is that, I just want the basic > display to work. What I am suppoesed to do for this. > Do I need to write HWcomposer, gralloc and framebuffer. > > If I am supposed to do this can anybody point me to some documents > regarding the same. > > Also will the display be up if I implement only gralloc and Framebuffer. > > Thank you, > Best Regards, > A G Megharaj > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
