How about a release?
The merger of r6xx-r7xx-support didn't seem to have any fallout (I'm not
counting acceleration issues of r[67]xx fallout, because that wasn't
available before, and it's not active by default).
So I think it's time for a new release. Are there any patches / git
branches missing, any important open issues (apart from usual bugs), are
you close to fixing/implementing something you'd like to have in the
next release? Now's the time to speak up.
I will enable DRI on r5xx by default now, 3D still has some issues, but
none of them seem to be radeonhd related. And it's *much* better
nowadays.
I think we can go for a 1.3 release as soon as r[67]xx acceleration is
stable enough to be switched on by default. For now 1.2.5 has to
suffice.
CU all
Matthias
--
Matthias Hopf
2009/3/10 Matthias Hopf
I will enable DRI on r5xx by default now, 3D still has some issues, but none of them seem to be radeonhd related. And it's *much* better nowadays.
How about http://bugs.freedesktop.org/show_bug.cgi?id=18097 ? I haven't tried it myself for a while, but I don't recall hearing an explicit fix for it in either the DDXs or DRM. I think we should get a conclusive state on the bug before the release. Cheers, -- Yang Zhao http://yangman.ca -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Yang Zhao writes:
I haven't tried it myself for a while, but I don't recall hearing an explicit fix for it in either the DDXs or DRM. I think we should get a conclusive state on the bug before the release.
Still there. Makes GL unusable on r5xx chips. One can get all the compositing goodness OK, which is an important use case for today's desktops, but the instant some poor sap with wobbly windows tries to run run a GL app he's going to be belly up. -- Alec Habig, University of Minnesota Duluth Physics Dept. habig@neutrino.d.umn.edu http://neutrino.d.umn.edu/~habig/ -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Mar 10, 09 11:20:55 -0500, Alec T. Habig wrote:
Still there. Makes GL unusable on r5xx chips. One can get all the compositing goodness OK, which is an important use case for today's desktops, but the instant some poor sap with wobbly windows tries to run run a GL app he's going to be belly up.
As Alex wrote in the bug this could be a DRM issue.
Matthias
--
Matthias Hopf
On Tue, Mar 10, 2009 at 11:04 AM, Matthias Hopf
The merger of r6xx-r7xx-support didn't seem to have any fallout (I'm not counting acceleration issues of r[67]xx fallout, because that wasn't available before, and it's not active by default).
So I think it's time for a new release. Are there any patches / git branches missing, any important open issues (apart from usual bugs), are you close to fixing/implementing something you'd like to have in the next release? Now's the time to speak up.
I will enable DRI on r5xx by default now, 3D still has some issues, but none of them seem to be radeonhd related. And it's *much* better nowadays.
I think we can go for a 1.3 release as soon as r[67]xx acceleration is stable enough to be switched on by default. For now 1.2.5 has to suffice.
Sounds good. Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Tue, Mar 10, 2009 at 11:04 AM, Matthias Hopf
wrote: The merger of r6xx-r7xx-support didn't seem to have any fallout (I'm not counting acceleration issues of r[67]xx fallout, because that wasn't available before, and it's not active by default).
So I think it's time for a new release. Are there any patches / git branches missing, any important open issues (apart from usual bugs), are you close to fixing/implementing something you'd like to have in the next release? Now's the time to speak up.
There is still the one regression we'd like to address.
However, I'm going skiing on Saturday for a week.
Now, at the end of this week, 3 possibilities arise:
- We release now, with the regression. I think that not too many people
are actually affected, so it is an option.
- We wait with the release until I'm back. Maybe Alex manages to fix the
regression until then.
- Somebody else does the release.
I, personally, would wait, another week doesn't sound too bad. Any
opinions?
Matthias
--
Matthias Hopf
Matthias Hopf writes:
Now, at the end of this week, 3 possibilities arise:
- We release now, with the regression. I think that not too many people are actually affected, so it is an option.
Wouldn't kill us - the work around (restart X) is easy, and if a release causes the bug to bite more people, you'll get more info about how to fix it. It's unlikely I'll have a chance to really run the git bisect process to ground today, but will try knowing you've got a deadline. Worse comes to worst, I'll also be on the road next week, and airplane time makes great debugging time (provided I get a local git repository ondisk before leaving :) -- Alec Habig, University of Minnesota Duluth Physics Dept. habig@neutrino.d.umn.edu http://neutrino.d.umn.edu/~habig/ -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
participants (4)
-
Alec T. Habig
-
Alex Deucher
-
Matthias Hopf
-
Yang Zhao