Re: Gtkradiant not working with radeon driver

2007-10-30 Thread Michel Dänzer
On Tue, 2007-10-30 at 02:33 +, Jose Rodriguez wrote: I´m not sure what do you mean by ddx [...] The X driver. For 3D, usually only the Mesa driver is relevant. I installed the xserver-xorg-video-ati-dbg and libc6-dbg packages [...] You need to install libgl1-mesa-dri-dbg or build from

Re: intel hw and caching interface to TTM..

2007-10-30 Thread Thomas Hellström
Dave Airlie wrote: Hi, So currently the TTM interface allows the user specify a cacheable allocation, and on Intel hardware this gets conflated with using the intel snooped memory type in the GART. This is bad as the intel snooped memory type comes with its own set of special rules and sucks

RE: Unknown symbol __you_cannot_kmalloc_that_much when compile drm against kernel 2.6.21

2007-10-30 Thread Wu, Nian
Jesse Barnes wrote: Sorry about that, a piece of code snuck into that commit that shouldn't have. Fixed in 6342e0507be177be309774aff0c31746beab73f6. It is OK now. Nian Jesse On Monday, October 29, 2007 1:49 am Wu, Nian wrote: Hi, Jesse, When compiled drm module against kernel

Re: intel hw and caching interface to TTM..

2007-10-30 Thread Dave Airlie
Dave, I'd like to see the flag DRM_BO_FLAG_CACHED really mean cache-coherent memory, that is cache coherent also while visible to the GPU. There are HW implementations out there (Poulsbo at least) where this option actually seems to work, althought it's considerably slower for things like

Re: intel hw and caching interface to TTM..

2007-10-30 Thread Keith Whitwell
Dave Airlie wrote: Dave, I'd like to see the flag DRM_BO_FLAG_CACHED really mean cache-coherent memory, that is cache coherent also while visible to the GPU. There are HW implementations out there (Poulsbo at least) where this option actually seems to work, althought it's considerably slower

Re: intel hw and caching interface to TTM..

2007-10-30 Thread Thomas Hellström
Dave Airlie wrote: Dave, I'd like to see the flag DRM_BO_FLAG_CACHED really mean cache-coherent memory, that is cache coherent also while visible to the GPU. There are HW implementations out there (Poulsbo at least) where this option actually seems to work, althought it's considerably slower

Re: intel hw and caching interface to TTM..

2007-10-30 Thread Dave Airlie
OK. We're using this functionality in Poulsbo, so we should probably sort this out to avoid breaking things. Okay I'll try and fix it back up tomorrow.. Yes, Eric seems to have the same opinion. I'm not quite sure I understand the reasoning behind it. Is it the added complexity or

Re: Gtkradiant not working with radeon driver

2007-10-30 Thread Jose Rodriguez
On Mon, 29 Oct 2007 22:50:06 +0100 Roland Scheidegger [EMAIL PROTECTED] wrote: Also, could you provide a backtrace from gdb? What are the max_index and min_index values? Er...not sure, there are a couple of values for each. Take a look below, please. On Tue, 30 Oct 2007 08:05:00 +0100 Michel

Re: intel hw and caching interface to TTM..

2007-10-30 Thread Thomas Hellström
Dave Airlie wrote: OK. We're using this functionality in Poulsbo, so we should probably sort this out to avoid breaking things. Okay I'll try and fix it back up tomorrow.. Yes, Eric seems to have the same opinion. I'm not quite sure I understand the reasoning behind

[Bug 12795] since Merge remote branch 'origin/master' into buffer-objects driver don't work

2007-10-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=12795 --- Comment #2 from [EMAIL PROTECTED] 2007-10-30 06:01 PST --- Is there any relation to bug #5714? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You

Re: Gtkradiant not working with radeon driver

2007-10-30 Thread Roland Scheidegger
Jose Rodriguez wrote: On Mon, 29 Oct 2007 22:50:06 +0100 Roland Scheidegger [EMAIL PROTECTED] wrote: Also, could you provide a backtrace from gdb? What are the max_index and min_index values? Er...not sure, there are a couple of values for each. Take a look below, please. #5 0xb69c9ad9

[Bug 12795] since Merge remote branch 'origin/master' into buffer-objects driver don't work

2007-10-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=12795 --- Comment #3 from [EMAIL PROTECTED] 2007-10-30 07:24 PST --- (In reply to comment #2) Is there any relation to bug #5714? I don't know, may be in this bug , this merge require xorg-server = 1.4 -- Configure bugmail:

[Bug 12877] Textures(?) in WoW breaking up until X-server is restarted

2007-10-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=12877 --- Comment #8 from [EMAIL PROTECTED] 2007-10-30 14:34 PST --- (In reply to comment #5) If this is a new issue you could try figuring out which commit caused it with git-bisect. I'm not sure that this is Mesa's fault because I've

[Bug 13012] New: unresolved symbol __driCreateNewScreen_20050727

2007-10-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13012 Summary: unresolved symbol __driCreateNewScreen_20050727 Product: Mesa Version: CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major

[Bug 13012] unresolved symbol __driCreateNewScreen_20050727

2007-10-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13012 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 13012] unresolved symbol __driCreateNewScreen_20050727

2007-10-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13012 --- Comment #2 from [EMAIL PROTECTED] 2007-10-30 19:17 PST --- (In reply to comment #1) It's not loading because the module versions are incompatible. You need to build X from git master to use Mesa from git master. Hi one