Bug 13312 - [i845G] EXA unaccelerated
Summary: [i845G] EXA unaccelerated
Status: RESOLVED DUPLICATE of bug 13389
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Wang Zhenyu
QA Contact: Xorg Project Team
Depends on:
Reported: 2007-11-20 02:17 UTC by Oswald Buddenhagen
Modified: 2008-01-26 02:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

log file (44.56 KB, text/plain)
2007-11-20 02:24 UTC, Oswald Buddenhagen
no flags Details

Description Oswald Buddenhagen 2007-11-20 02:17:32 UTC
seems like the driver decided that my chip has no 2d accelerator. :}
everything is just so incredibly slow ...

XAA seems to work fine (speed-wise).
Comment 1 Oswald Buddenhagen 2007-11-20 02:24:59 UTC
Created attachment 12648 [details]
log file
Comment 2 Wang Zhenyu 2007-11-20 18:05:53 UTC
yeah, for 830G and 845G, the hardware doesn't support texture format like a8,x8r8g8b8,x8b8g8r8. So there would be lots of fallbacks in those cases, and
we're fixing to use batch buffer instead of looping ring buffer a lot.
Try to use Option "EXANoComposite" "true" as a workaround for now.
Comment 3 Oswald Buddenhagen 2007-11-21 01:36:43 UTC
adding this option didn't help - little surprisingly, as compositing is completely disabled anyway (as you should have found in the log ;).

the resolution doesn't seem appropriate ... if you release the driver in this state, you will ridicule yourself. ;)
Comment 4 Oswald Buddenhagen 2007-12-03 11:33:42 UTC
you should seriously consider to reopen the bug and add it to the 2.2.1 blocker list *now*, so it doesn't fall through the cracks.
really, the driver is hardly usable now. it's like a remote session over 10 mbit lan.
Comment 5 Oswald Buddenhagen 2008-01-26 02:52:52 UTC
Comment 6 Oswald Buddenhagen 2008-01-26 02:53:32 UTC
hey, *i* was first. oh, well. :)

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

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.