Bug 1192 - remove optional cfb support from drivers
Summary: remove optional cfb support from drivers
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high enhancement
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1245
  Show dependency treegraph
 
Reported: 2004-08-26 08:55 UTC by Adam Jackson
Modified: 2004-09-16 03:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
kill-cfb-1.patch (28.05 KB, patch)
2004-08-26 08:56 UTC, Adam Jackson
no flags Details | Splinter Review
kill-cfb-2.patch (96.65 KB, patch)
2004-08-26 22:33 UTC, Adam Jackson
no flags Details | Splinter Review
kill-cfb-3.patch (108.14 KB, patch)
2004-08-30 20:12 UTC, Adam Jackson
no flags Details | Splinter Review

Description Adam Jackson 2004-08-26 08:55:26 UTC
this patch removes cfb support from the six drivers where its use is an option -
i740, nsc, s3, s3virge, siliconmotion, and via.  cuts 600 lines of dead code. 
for all but s3virge cfb is a compile-time option.  no one wants to use cfb
anyway, it's slow and lacks Render support.
Comment 1 Adam Jackson 2004-08-26 08:56:06 UTC
Created attachment 736 [details] [review]
kill-cfb-1.patch
Comment 2 Adam Jackson 2004-08-26 09:11:35 UTC
as a side effect this kills the last user of xf24_32bpp, which is another ~800 LoC.
Comment 3 Adam Jackson 2004-08-26 22:33:17 UTC
Created attachment 739 [details] [review]
kill-cfb-2.patch

extends the previous patch to also remove xf24_32bpp, since it's now useless.
Comment 4 Adam Jackson 2004-08-30 20:12:41 UTC
Created attachment 783 [details] [review]
kill-cfb-3.patch

more cleanup, delete some header references and dead code, and fix comments to
refer to fb instead of cfb.
Comment 5 Adam Jackson 2004-09-16 20:05:27 UTC
applied, along with some Imakefile cleanup.


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.