Aapo Tahkola wrote:
On Sat, 11 Mar 2006 22:48:49 +0100
Rune Petersen <[EMAIL PROTECTED]> wrote:
All this is just a symptom of dri tex heap manager. nwn will reload textures
but they will be given different locations on vram.
You can print out t->offset at around line 506 of r300_texmem.c if you are
interested in seeing how it behaves.
But if you do keep in mind that you need to do it after UNLOCK_HARDWARE or else
bad things will happen.
You should check that Ben's fix is kicking in by looking for message saying:
"Setting GART location based on new memory map" in dmesg.
If you still see problems with it enabled you can confirm GART overlapping by loading
drm.ko with DEBUG=1 (AFAIK) and compairing dev_priv->gart_vm_start against
dev_priv->fb_location and dev_priv->fb_size .
DRM doesnt print these values but you can calculated it based on Xorg log.
Find line that says:
(II) RADEON(0): Will use x kb for textures at offset x
and compaire upper bound of that against dev_priv->gart_vm_start.
Me stupid, there is a module-path in xorg.conf and I forgot to change i
to the new path.
Now nwn looks nice, and all games works (ut2k? still have corruption(?)
on some textures).
I really sorry about this.....
Rune Petersen
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
