Re: [Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Svante Signell
Additional info, this shows up in the XFree86.0.log file: (II) SAVAGE(0): [drm] Could not create dummy context On Wed, 2004-04-07 at 08:07, Svante Signell wrote: > On Wed, 2004-04-07 at 01:08, Svante Signell wrote: > > On Wed, 2004-04-07 at 00:53, Felix Kühling wrote: > > ... > > > I suspect there

Re: [Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Svante Signell
On Wed, 2004-04-07 at 01:08, Svante Signell wrote: > On Wed, 2004-04-07 at 00:53, Felix Kühling wrote: > ... > > I suspect there was a configuration change on the snapshot build machine > > that made the build fail after April 1. I just committed a workaround to > > the snapshot build scripts. Unof

t_vertex conversion for R200 (was Re: [Dri-devel] [r200] Viewperf-7.1.1 numbers - Not so good.)

2004-04-06 Thread Ian Romanick
Dieter Nützel wrote: Anyone working on the "t_vertex" conversion for radeon (r200)? Then Andreas could do his TMU3 work, again. Which could help with Viewperf. I started looking at this today. I decided to start with just the swtcl path. I'm a bit confused (already). All of the drivers that ha

Re: [Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Svante Signell
On Wed, 2004-04-07 at 00:53, Felix Kühling wrote: ... > I suspect there was a configuration change on the snapshot build machine > that made the build fail after April 1. I just committed a workaround to > the snapshot build scripts. Unofficial up-to-date snapshots are > available from http://freed

Re: [Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Felix Kühling
On Tue, 06 Apr 2004 22:50:35 +0200 Svante Signell <[EMAIL PROTECTED]> wrote: > On Tue, 2004-04-06 at 12:36, Felix Kühling wrote: [snip] > Thanks, the problem is a missing symbol: > libGL: XF86DRIGetClientDriverName: 1.1.16 savage (screen 0) > libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/sa

[Dri-devel] annoying build problem

2004-04-06 Thread Mark Cass
dri-devel,   i am having a rebuild problem. not sure what the trigger is but here is the problem. i do a make World in /xc/xc and get an error related to HPkeysyms.h. make says it can't find the file. i copied all the header files into /xc/xc/include and that problem goes away, but then i get

Re: [Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Svante Signell
On Tue, 2004-04-06 at 12:36, Felix Kühling wrote: > The kernel messages look harmless. Since XFree86.0.log reports DRI > enabled the problem is either due to a wrong libGL or a broken 3D > driver. Or maybe the 3D driver doesn't have permission to access the > kernel driver. Could you run > > LIB

[Dri-devel] [Bug 512] Video crashes xinerama system

2004-04-06 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=512 --- Additional Comments From [EMAIL PROTECTED] 2004-04-06 16:06 --- I've found anothe

Re: [Dri-devel] glpointsize broken on my r250

2004-04-06 Thread Ian Romanick
Paul Heldens wrote: And yes I understand the fault is not dri's and not the application developer, but the hardware. (correct this if I'm wrong) As I said before, THE FAULT IS 100% WITH THE APPLICATION DEVELOPER. OpenGL provides a mechanism to determine the maximum supported point size. The dri

[Dri-devel] Where dri parts reside now.

2004-04-06 Thread Jacek Rosik
Hi, For some time i haven't been paying much attention to dri development. I'm need to do some work now but I'm little lost. From my little investigation I presume that situation looks more less like this. * 3d driver development was moved to mesa tree, bu it needs dri tree in order to compile.

Re: [Dri-devel] glpointsize broken on my r250

2004-04-06 Thread Roland Scheidegger
Felix Kühling wrote: On Mon, 05 Apr 2004 14:50:45 -0700 Ian Romanick <[EMAIL PROTECTED]> wrote: Paul Heldens wrote: I found on the list that this has always been broken in dri because of a hardware issue.(?) Example of affected apps; gtkradiant, blender,maya(hearsay) Questions: Is there any ot

Re: [Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Felix Kühling
The kernel messages look harmless. Since XFree86.0.log reports DRI enabled the problem is either due to a wrong libGL or a broken 3D driver. Or maybe the 3D driver doesn't have permission to access the kernel driver. Could you run LIBGL_DEBUG=verbose glxinfo The output should tell what's wrong.

Re: [Dri-devel] glpointsize broken on my r250

2004-04-06 Thread Felix Kühling
On Tue, 06 Apr 2004 12:24:09 +0200 Paul Heldens <[EMAIL PROTECTED]> wrote: > On Tue, 2004-04-06 at 00:33 +0200, Felix Kühling wrote: > > > I can't test it right now, but IIRC the radeon drivers even limit the > > size of antialiased points to 1. This seems to be compliant with the > > specs, but

Re: [Dri-devel] glpointsize broken on my r250

2004-04-06 Thread Paul Heldens
On Tue, 2004-04-06 at 00:33 +0200, Felix KÃhling wrote: > I can't test it right now, but IIRC the radeon drivers even limit the > size of antialiased points to 1. This seems to be compliant with the > specs, but wouldn't it be nicer to draw antialiased points as software > fallbacks and not limit

[Dri-devel] [Bug 314] 3D support for Radeon IGP chips

2004-04-06 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=314 --- Additional Comments From [EMAIL PROTECTED] 2004-04-06 03:44 --- Hi again, Thanks

[Dri-devel] ProSavage KM133: no direct rendering?

2004-04-06 Thread Svante Signell
Hello, I installed and built the latest savage snapshot savage-20040401-linux.i386.tar.bz2 from www.freedesktop.org/~dri/snapshots together with the extras/XFree86.bz2 dated 29-Sep-2003. XFree86 packages installed are Debian/testing 4.3.0-7. The XV stuff seem to work OK at 16 bits, but at 24 bit