And suddenly WoW is working with R300 again!

[Chris Rankin]

Hi,

WoW has been crashing at start-up with "invalid drawables" (OpenGL mode) for ages, but suddenly it's started working again. However, I am still seeing texturing errors in certain locations that look like random blotches dancing all over the place. This is actually an improvement: before WoW started refusing to run at all, these same textures were uniformly blue instead.

So basically, there's still something wrong somewhere with R300 texturing.

Cheers,
Chris



      __________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

[Nicolai Hähnle]

Hi!

Am Sonntag 29 Juni 2008 23:37:11 schrieb Chris Rankin:
> WoW has been crashing at start-up with "invalid drawables" (OpenGL mode)
> for ages, but suddenly it's started working again. However, I am still
> seeing texturing errors in certain locations that look like random blotches
> dancing all over the place. This is actually an improvement: before WoW
> started refusing to run at all, these same textures were uniformly blue
> instead.

Seems like this is something for the program support matrix...

> So basically, there's still something wrong somewhere with R300 texturing.

I'm not too surprised. Two immediate comments:

1. We have to get texture tiling into shape anyway for the RS690, so we might
as well just do this (I seriously don't have time for it though, as there are
so many other things to take care of).

2. Is there any chance someone (you?) can analyze and isolate the problem
you're seeing in WoW? Since it's likely that other games are affected as
well, it would be nice to have a simple test that indicates failure. BTW: do
try running Piglit and compare its results with the results on
http://people.freedesktop.org/~nh/piglit/r300/ - there's always the chance
that we already *have* a test case for this texturing problem, but that it
passes on my test setup due to some subtle hardware difference. Yes, it's
unlikely, but it could save us a lot of unnecessary debugging time.

cu,
Nicolai

> Cheers,
> Chris
>
>
>
>       __________________________________________________________
> Not happy with your email address?.
> Get the one you really want - millions of new email addresses available now
> at Yahoo! http://uk.docs.yahoo.com/ymail/new.html



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

[Phil Armstrong]

Nicolai Hähnle <nhaehnle@...> wrote:
> Am Sonntag 29 Juni 2008 23:37:11 schrieb Chris Rankin:
>> So basically, there's still something wrong somewhere with R300 texturing.
>
> I'm not too surprised. Two immediate comments:
>
> 1. We have to get texture tiling into shape anyway for the RS690, so we might
> as well just do this (I seriously don't have time for it though, as there are
> so many other things to take care of).

Just for my own personal use (*ahem* playing Half-Life 2 under wine)
I've been keeping the radeon tiling patches from bugzilla up to date
with the mesa / drm git master HEADs.

I haven't cleaned up the patches though: in particular, they add a new
object to the radeon drm kernel interface, which presumably requires
bumping the interface version number.

If people want me to have a shot at kicking these patches into shape
so that they can be merged into current mesa, then I can give it a go,
but I'll need some guidance as towhat's needed -- is the userland
expected to be backwards compatible with older drm kernel interfaces
for instance? Alternatively, the git archive in question is publically
available if people want to pull from it.

Also note that I didn't write these patches in the first place, so I
can't vouch for them in full (although they've been perfectly stable
for me).

cheers, Phil

--
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

[Stephane Marchesin]

On Tue, Jul 22, 2008 at 2:35 PM, Phil Armstrong <phil-news@...> wrote:

> Nicolai Hähnle <nhaehnle@...> wrote:
>> Am Sonntag 29 Juni 2008 23:37:11 schrieb Chris Rankin:
>>> So basically, there's still something wrong somewhere with R300 texturing.
>>
>> I'm not too surprised. Two immediate comments:
>>
>> 1. We have to get texture tiling into shape anyway for the RS690, so we might
>> as well just do this (I seriously don't have time for it though, as there are
>> so many other things to take care of).
>
> Just for my own personal use (*ahem* playing Half-Life 2 under wine)
> I've been keeping the radeon tiling patches from bugzilla up to date
> with the mesa / drm git master HEADs.
>
> I haven't cleaned up the patches though: in particular, they add a new
> object to the radeon drm kernel interface, which presumably requires
> bumping the interface version number.

Yes.

>
> If people want me to have a shot at kicking these patches into shape
> so that they can be merged into current mesa, then I can give it a go,
> but I'll need some guidance as towhat's needed -- is the userland
> expected to be backwards compatible with older drm kernel interfaces
> for instance?

Yeah, you have to do that. Look at the r100 & r200 drivers, they
already handle texture tiling with backwards compatibility.

Stephane

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev