Bug 1259 - convert sunleo to fb
Summary: convert sunleo to fb
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/other (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high enhancement
Assignee: Xorg Project Team
QA Contact:
Depends on:
Blocks: 1245
  Show dependency treegraph
Reported: 2004-08-31 12:19 UTC by Adam Jackson
Modified: 2005-02-02 10:35 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:

sunleo-conversion-1.patch (19.95 KB, patch)
2004-08-31 12:19 UTC, Adam Jackson
no flags Details | Splinter Review
sunleo-conversion-2.patch (37.82 KB, patch)
2004-09-28 16:10 UTC, Adam Jackson
no flags Details | Splinter Review

Description Adam Jackson 2004-08-31 12:19:14 UTC
attached patch converts sunleo(4) to cfb.  this and bug #1192 are it for
low-hanging cfb fruit in the drivers, all the remaining cfb users (sunffb, mga,
glint, chips) need it for overlay support.

the custom GC handling in cfb doesn't translate to fb, so it's gone.  i suspect
this leaves the driver more or less unaccelerated, but fb should be slightly
faster on its own so it may be a wash.  shadowfb would be easy to add,
converting the GC code to XAA would be harder.  i'd be happy to go as far as
shadowfb and then wait for a better AA to present itself.

untested for lack of hardware, but compiles with a minimum of external symbols,
should at least load.
Comment 1 Adam Jackson 2004-08-31 12:19:41 UTC
Created attachment 795 [details] [review]
Comment 2 Adam Jackson 2004-09-28 16:10:04 UTC
Created attachment 978 [details] [review]

slightly cleaner patch, deletes some dead code.  still no shadowfb yet.

testers sought.
Comment 3 Adam Jackson 2004-11-22 12:48:49 UTC
weeve@gentoo has tested this and reports that his cat still has all its fur.

i'll take a hack at adding shadowfb support too, but this looks good enough to
push into 6.9 as is.
Comment 4 Adam Jackson 2005-01-13 22:21:19 UTC
applied to head, closing.

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.