Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
------- Additional Comments From mharris@... 2006-07-26 06:56 -------
(In reply to comment #16)
> (In reply to comment #15)
> Come on, disabling "DRI" completely is not an acceptable suggestion. This is
> maybe admissible for fixing
> as a distribution related patch in order to ensure the necessary reliability for
> upcoming FC6. Upstream "bugs.freedesktop.org" is the place to investigate the
> issue and to actually track down the bug.
There seems to be a misunderstanding here, so let me try to resolve it
by explaining things, at least how I see it.
The savage driver seems to have regressed at some point, and it appears
that it was due to the integration of DRI support for newer hardware
from the troubleshooting present in the linked Red Hat bug report and
this one. Ultimately, the only "good" solution is for the savage driver
to be fixed so that there are no problems with or without DRI on any
hardware. Additionally, IMHO at least, the driver should "just work"
by default on all hardware without requiring the end user to provide
any special configuration options.
That would be the ideal situation at least. Right now however, there is
no real fix available yet, so it makes sense to provide users with a
workaround if possible. Disabling DRI on the affected systems seems to
work around the issue, so in order to have an out of the box working
setup for /all/ Fedora users, it makes sense to disable DRI by default
on the chips which have been reported to not work properly if DRI is
enabled, until there is a better fix available.
My untested patch intends to disable DRI by default on the chips that
are known to not work right when it is enabled, and to allow users
to forcibly re-enable DRI by configuration if desired. This patch
was intended as a Fedora workaround until a newer savage driver is
available upstream at X.Org which has resolved the problem. Since the
problem isn't Fedora specific, and also since I'd like other people
to test it who may or may not be using Fedora, I commented about my
proposed workaround here to give others the opportunity to test it,
and in case other distributions were interested in the workaround as
Wether X.Org is interested in providing this workaround in the official
savage driver or not does not matter to me. Personally I'd prefer to
see a proper fix than have the workaround, but right now for Fedora at
least we need a workaround until a proper fix is available.
I only attached the patch here because Daniel asked me to. If I had written
the patch with the intention of getting X.Org to include it in the official
driver, I'd have attached the patch to the bug report initially, and explicitly
asked for it to be committed to CVS. I didn't do that however, as that was
not my intention.
Hopefully this clarifies any misunderstanding you have now.
> I recall that the current issue was not present in "Xorg 7.0". It is
> hence a mere regression with respect to a previous, working release.
Hopefully that will help those working on Savage DRI support to narrow
down the problem and fix it in a future driver update. Once a fix is
available, we can disable the Fedora workaround.
I'm still interested in good/bad feedback from those affected by the
problem as to wether the patch works right for them or not. It's in
rawhide right now.
Thanks in advance.
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.