Makes sense... Excuse my poor english, does the following comment mean copybit backend for SF be released as part of Donut or is this a post-Donut feature?
"HOWEVER, on the release after Donut, the copybit module won't be used by SurfaceFlinger directly instead it will be used as a back-end for our software OpenGL ES 1.x" Thanks, Cemil On Jun 9, 12:33 am, pixelflinger <pixelflin...@google.com> wrote: > Hello, > > On Jun 8, 2:13 pm, cemil <cemil_azizo...@yahoo.com> wrote: > > > Hi Mathias, > > > I'd like to clarify one point. If we implementcopybit, will this only > > benefit SurfaceFlinger and not the (Java) apps? AFAIK, java apps use > > skia middleware. Does skia backend make use ofcopybitsomehow? I > > can't see this in the code, but want to confirm. If that's true, what > > mechanisms are there for blit acceleration for apps? > > Copybitis only used in SurfaceFlinger when OpenGL ES cannot be used > or when it's software. > Actually in the current implementation (cupcake), SurfaceFlinger > always usescopybitinstead of GL ifcopybitis available -- but > that's an oversight. > > There are no mechanism to accelerate applications at the moment. Skia > is a purely software renderer. It can greatly benefit from newer CPUs > though, which have SIMD instructions, often, it'll be able to operate > at bus speed in that case. We're working on optimization in that area. > > If a device has a GPU, it makes no sense to implementcopybit, because > (1) it won't be used by apps and (2) SurfaceFlinger already uses the > GPU for its work. Now, if the device has an additional 2D part (like > the G1), it is useful to implementcopybit, this way application won't > have to share the GPU with SurfaceFlinger. > > Mathias > > > > > Thanks, > > Cemil > > > On May 22, 3:52 am, pixelflinger <pixelflin...@google.com> wrote: > > > > Hi, > > > > copybitis just an abstraction for a basic 2D blitter with support for > > > rotation, scaling and color/pixelformat conversions. These features > > > can be supported in full or partially. > > > > If thecopybitmodule is present, then SurfaceFlinger will try to use > > > it instead of using OpenGL ES. > > > > On the G1copybitis used for all window compositions and video > > > playback (CC and scaling), on this h/wcopybitis very fast and > > > provide very good up and down scaling. > > > > HOWEVER, on the release after Donut, thecopybitmodule won't be used > > > by SurfaceFlinger directly, instead it will be used as a back-end for > > > our software OpenGL ES 1.x and SurfaceFlinger will only use the OpenGL > > > ES API. > > > Eventually, thecopybitmodule will be phased out, instead, we will > > > ask the ISV/OEMs to implement these features on their OpenGL ES > > > drivers, if they think it is necessary. > > > > If your h/w doesn't have accelerated GL, but has some sort of decent > > > 2D blitter, you can write acopybitHAL module for it, and it will be > > > used automatically by SurfaceFlinger -- at least under cupcake and > > > donut. > > > > Mathias > > > > On May 20, 8:57 pm, Wenlong Li <wenl...@gmail.com> wrote: > > > > > Should I send this message to this group? anyone can help answer my > > > > question. thx very much > > > > > On Wed, May 20, 2009 at 6:17 PM, Wenlong Li <wenl...@gmail.com> wrote: > > > > > Hello, > > > > > > Can anyone share some info aboutcopybit? I saw there is a header file > > > > > (copybit.h) under hardware directory, but don't know the detailed > > > > > implementation. I guess the main operation is to copy image from > > > > > source to destination, and scale image. Is my understanding correct? > > > > > > Besides these, can it support image format conversion, such as from > > > > > YUV to RGB. Seems camera capatures image in YUV format, and does > > > > > conversion before showing it in screen. > > > > > > The third question is which device is used forcopybit? GPU or other > > > > > devices? > > > > > > thx, > > > > > Wenlong --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
