Bug 7359 - File r300_render.c function r300Fallback line 486
Summary: File r300_render.c function r300Fallback line 486
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL: http://digilander.libero.it/vezza
Depends on:
Reported: 2006-06-29 03:39 UTC by Andrea V.
Modified: 2006-06-29 05:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Note You need to log in before you can comment on or make changes to this bug.
Description Andrea V. 2006-06-29 03:39:22 UTC
Hardware 3d acceleration is enabled and works fine with glxgears but when I
start a 3d sofware like google-earth it falls back into sofware rendering with
the following error:

File r300_render.c function r300Fallback line 486
Software fallback:ctx->Line.SmoothFlag

visit this link http://digilander.libero.it/vezza for xorg.conf and xorg.0.log

My system is a P4 3,0 Ghz 1,5Gb RAM with ATI RADEON 9800SE video card
Comment 1 multinymous 2006-06-29 03:49:58 UTC
Same here with Google Earth. Commenting out that line in r300_render.c enables
Comment 2 Jerome Glisse 2006-06-29 04:39:52 UTC
By commenting out you have accelerated line drawing but not smooth line drawing
even though with hight screen resolution and small linewidth you probably won't
see the difference.

Anyway the message you see doesn't mean it fallback fully in software rendering
just that smooth line are drawed using software. So please don't report bug for
that. This are functionality not yet implemented.
Comment 3 multinymous 2006-06-29 05:30:40 UTC
The current situation is that unpatched Mesa r300 provides horrible performance
for an important application. Until the functionality is implemented, perhaps
there should be a runtime config option to ignore the flag instead of falling
back to software rendering?

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.