Bug 4152 - 24bpp broken with fbcompose.c
Summary: 24bpp broken with fbcompose.c
Status: RESOLVED DUPLICATE of bug 3944
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xorg (show other bugs)
Version: 6.99.99.900 (7.0 RC0)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
: 4862 4870 (view as bug list)
Depends on:
Blocks: 1690
  Show dependency treegraph
 
Reported: 2005-08-20 01:15 UTC by Tejas Kokje
Modified: 2005-11-29 20:58 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Tejas Kokje 2005-08-20 01:15:06 UTC
I am using CVS snapshot of 2005-08-10 with Mandriva Linux. My intel 810 graphics card 
does not display 24 bit depth properly. The colors are odd and the screen does not 
refresh smoothly leaving impressions of the previous screen. However it works fine with 
16 bit depth. 
 
My card worked fine with 24 bit depth on xorg 6.8.
Comment 1 George Lindholm 2005-09-16 12:47:40 UTC
I see the same problem with my ATI 9000 Radeon card and the
2005/09/13 snapshot from Mandrivia
Comment 2 Alan Hourihane 2005-10-24 11:00:28 UTC
*** Bug 4862 has been marked as a duplicate of this bug. ***
Comment 3 Alan Hourihane 2005-10-24 12:37:58 UTC
This is a generic bug, affecting all chipsets that use 24bpp pixmaps. Seems to
have gotten broken since 6.8.2.

Having had a few minutes to look. It seems that the fb code is borked in
fbcompose.c. And it doesn't appear to be the new MMX functions as I've compiled
without them and it still happens.
Comment 4 Alan Hourihane 2005-10-25 01:46:21 UTC
*** Bug 4862 has been marked as a duplicate of this bug. ***
Comment 5 Adam Jackson 2005-11-19 04:52:06 UTC
*** Bug 4870 has been marked as a duplicate of this bug. ***
Comment 6 Adam Jackson 2005-11-30 15:58:06 UTC
man, this issue comes up a lot

*** This bug has been marked as a duplicate of 3944 ***


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.