#1547 BLOC Future : Decide frame buffer depth - 565 vs ARGB 8888

[Zarro Boogs per Child]

#1547: Decide frame buffer depth - 565 vs ARGB 8888
---------------------------------------+------------------------------------
           Reporter:  jg               |       Owner:  cjb           
               Type:  task             |      Status:  new           
           Priority:  blocker          |   Milestone:  Future Release
          Component:  x window system  |     Version:                
         Resolution:                   |    Keywords:                
        Next_action:  never set        |    Verified:  0             
Deployment_affected:                   |   Blockedby:                
           Blocking:                   |  
---------------------------------------+------------------------------------
Changes (by skierpage):

  * next_action:  => never set


Comment:

 What was the resolution of this bug?  Back in 2007, Dan Williams in the
 thread "Cairo tile engine, and accessing 565 buffers from cairo and C"
 wrote "we'll be hopefully moving to 24-bit color when we switch to the
 LX".

 But according to Xorg.0.log and the xdpyinfo command in 8.2.1 on a C2
 XO-1, the Geode LX framebuffer depth and bpp are both 16, and the default
 X11 visual is RGB 565 (TrueColor 16 planes deep).  I don't know what the
 "native" XRender format is.

 The Cairo and pixman rendering libraries continue to gain optimizations
 for 16bpp, though not as much as for 24 and 32-bit formats.  Also there
 are patches for XULRunner (Firefox) to "Enable 16bpp (or native visual
 xrender fmt)", Mozilla bugs 386440 and 491357.  Those should be taken into
 account if and when this bug is re-decided.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1547#comment:11>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system