Bug 14093

Summary: Drawing Error with PIXELFORMAT
Product: cairo Reporter: Shining <nshi>
Component: directfb backendAssignee: cairo-bugs mailing list <cairo-bugs>
Status: RESOLVED MOVED QA Contact: cairo-bugs mailing list <cairo-bugs>
Severity: major    
Priority: high    
Version: 1.4.14   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: desc.pixelformat = DSPF_RGB16
desc.pixelformat = DSPF_RGB32;
Source Code

Description Shining 2008-01-15 21:47:43 UTC
Created attachment 13739 [details]
desc.pixelformat = DSPF_RGB16

My Development Eviroment: 
   vmware 6.0.1
   Debian Sarge 3.1a6 with framebuffer support
   Kernel boot parameters is : 
      kernel /boot/bzImage-2.4.27-rtl3.2-rc1 root=/dev/sda1 ro vga=785
   Cairo 1.4.14 compile parameters is: 
      ./configure --enable-xlib=no \
                  --enable-xlib-xrender=no \
                  --enable-directfb=yes \
                  --enable-pdf=no \
                  --enable-svg=no
   exceed on WindowXP sp2
   DirectFB 1.0.1 (/etc/directfbrc is setting "system=sdl")
   
MyTaret:
   I try to run cairo-snippets with the DirectFB backend.

After several tests, I found that the corrent display of cairo-snippet is relative with the PIXELFORMAT value of the DIRECTFB. 

according to diffirent PIXELFORMAT value, some result can be displayed correctly and some can not be displayed properly.

In the attached program, if the 
   "desc.pixelformat = DSPF_RGB16;" 
the result isn't corrent(see "rgb16.png" ), and 
if the "desc.pixelformat = DSPF_RGB32;",the result is corrent(see "rgb32.png").

The same problem is the same with the framebuffer device.
Comment 1 Shining 2008-01-15 21:48:20 UTC
Created attachment 13740 [details]
desc.pixelformat = DSPF_RGB32;
Comment 2 Shining 2008-01-15 21:50:13 UTC
Created attachment 13741 [details]
Source Code
Comment 3 GitLab Migration User 2018-08-25 13:33:26 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/64.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.