Re: [Dri-devel] R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied

2002-10-09 Thread Ilia Zadorozhko
On Tuesday 08 October 2002 17:52, Jens Owen wrote: Ilia Zadorozhko wrote: Hi people, Help me please getting DRI to work. I've installed latest (rage128-20021008-linux.i386.tar.bz2) versions of DRI. Function drmSetBusid requires some kind of permission, which I can't understand.

Re: [Dri-devel] waiting for anoncvs_dri's still there ;-(

2002-10-09 Thread Keith Whitwell
Brian Paul wrote: Dieter Nützel wrote: cvs update M xc/config/cf/host.def M xc/config/cf/xf86site.def M xc/config/cf/xfree86.cf P xc/lib/GL/mesa/src/drv/r200/r200_ioctl.c cvs server: [16:53:25] waiting for anoncvs_dri's lock in /cvsroot/dri/xc/xc/lib/GLw cvs server: [16:53:55] waiting

Re: [Dri-devel] waiting for anoncvs_dri's still there ;-(

2002-10-09 Thread Keith Whitwell
Keith Whitwell wrote: Brian Paul wrote: Dieter Nützel wrote: cvs update M xc/config/cf/host.def M xc/config/cf/xf86site.def M xc/config/cf/xfree86.cf P xc/lib/GL/mesa/src/drv/r200/r200_ioctl.c cvs server: [16:53:25] waiting for anoncvs_dri's lock in /cvsroot/dri/xc/xc/lib/GLw cvs

Re: [Dri-devel] driver feature table

2002-10-09 Thread Ian Romanick
On Wed, Oct 09, 2002 at 07:57:18AM -0600, Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Maybe one of the web masters can incorporate it into the website. Couple quick corrections. I don't think R200 supports

Re: [Dri-devel] driver feature table

2002-10-09 Thread Keith Whitwell
Ian Romanick wrote: On Wed, Oct 09, 2002 at 07:57:18AM -0600, Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Maybe one of the web masters can incorporate it into the website. Couple quick corrections. I don't think R200 supports

Re: [Dri-devel] driver feature table

2002-10-09 Thread Brian Paul
Ian Romanick wrote: On Wed, Oct 09, 2002 at 07:57:18AM -0600, Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Maybe one of the web masters can incorporate it into the website. Couple quick corrections. I don't think R200 supports

Re: [Dri-devel] driver feature table

2002-10-09 Thread Jens Owen
Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Thanks Brian. Here are some more corrections: 1) Driver headings on top row: It looks like the driver names were based on some common names we throw around when talking about these

Re: [Dri-devel] driver feature table

2002-10-09 Thread Brian Paul
Jens Owen wrote: Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Thanks Brian. Here are some more corrections: 1) Driver headings on top row: This was intended to be interpreted as chipsets, not drivers. By that reasoning, I

Re: [Dri-devel] driver feature table

2002-10-09 Thread Michel Dänzer
On Mit, 2002-10-09 at 15:57, Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Here's the data for PowerPC: r200: ? (should basically work, but probably some bugs left) r100: yes r128: yes i8xx: no mga ? (probably doesn't work, but

[Dri-devel] Mesa 4.1 branch

2002-10-09 Thread Brian Paul
I've created a new DRI branch: mesa-4-1-branch I'm in the process of porting all the DRI drivers to the new Mesa 4.1 code. I'll be checking in changes soon, but don't expect anything to run or even compile. I'll post again when I think it's usable. -Brian

Re: [Dri-devel] driver feature table

2002-10-09 Thread Michel Dänzer
On Mit, 2002-10-09 at 17:49, Brian Paul wrote: Jens Owen wrote: Brian Paul wrote: ATI r128 Column: Was support for Pro cards ever completed? I know the initial driver did not have it. Pro is listed on DRI Status page: http://dri.sourceforge.net/dri_status.phtml It used to work

Re: [Dri-devel] driver feature table

2002-10-09 Thread Brian Paul
Keith Whitwell wrote: Ian Romanick wrote: On Wed, Oct 09, 2002 at 07:57:18AM -0600, Brian Paul wrote: I've whipped up an HTML table which summarizes the features of the DRI drivers. Maybe one of the web masters can incorporate it into the website. Couple quick corrections. I don't

[Dri-devel] drm_os_linux.h: max() macro?

2002-10-09 Thread Brian Paul
in drm_os_linux.h in the DRM_WAIT_ON macro there's: schedule_timeout(max(HZ/100,1)); \ Where is max() supposed to be defined? It's undefined when I compile here. Replacing it with: schedule_timeout((HZ/100 1) ? HZ/100 : 1);\ seems to work.

Re: [Dri-devel] drm_os_linux.h: max() macro?

2002-10-09 Thread Keith Whitwell
Brian Paul wrote: in drm_os_linux.h in the DRM_WAIT_ON macro there's: schedule_timeout(max(HZ/100,1)); \ Where is max() supposed to be defined? It's undefined when I compile here. Replacing it with: schedule_timeout((HZ/100 1) ? HZ/100 : 1);\ Sounds

Re: [Dri-devel] driver feature table

2002-10-09 Thread Jens Owen
Brian Paul wrote: If anyone else wants to make changes, do so, and post a new table.html file. Okay. Here's a new file. It contains the following fixes: 1) i830 chipset uses i830 kernel module. 2) Michael's PowerPC support row. -- /\ Jens Owen

Re: [Dri-devel] waiting for anoncvs_dri's still there ;-(

2002-10-09 Thread Eric Anholt
On Wed, 2002-10-09 at 02:15, Keith Whitwell wrote: Keith Whitwell wrote: Brian Paul wrote: Dieter Nützel wrote: cvs update M xc/config/cf/host.def M xc/config/cf/xf86site.def M xc/config/cf/xfree86.cf P xc/lib/GL/mesa/src/drv/r200/r200_ioctl.c cvs server: [16:53:25] waiting

Re: [Dri-devel] driver feature table

2002-10-09 Thread Michel Dänzer
On Mit, 2002-10-09 at 19:29, Jens Owen wrote: 2) Michael's PowerPC support row. I assume you're talking about me. ;) I think it's a bad idea to just say 'no' for drivers that aren't 100% known to work, because people will think 'doh, it doesn't work, no point in trying'. In particular, I'd

Re: [Dri-devel] driver feature table

2002-10-09 Thread Adam K Kirchhoff
On Wed, 9 Oct 2002, Jens Owen wrote: Brian Paul wrote: If anyone else wants to make changes, do so, and post a new table.html file. Okay. Here's a new file. It contains the following fixes: 1) i830 chipset uses i830 kernel module. 2) Michael's PowerPC support row. Is each card

[Dri-devel] Re: driver feature table

2002-10-09 Thread Smitty
Hi Brian Attached is an updated table. Good work, when everyone stops pointing out typos etc please email (cc) me a copy, and I'll put it up sometime (wee bit busy atm). Liam it depends --- This sf.net email is sponsored by:ThinkGeek

[Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock

2002-10-09 Thread Pawel Salek
Hi, I have got a following messages on boot with current snapshot radeon-20021009, running with ATI Radeon Mobility M6 LY rev 0, stock RH8.0 kernel (2.4.18-14 with a whole lot of patches). modprobe: modprobe: Can't locate module char-major-226 last message repeated 3 times kernel: Linux

Re: [Dri-devel] Quake3 1.32, r_smp 1, mga (G550) error

2002-10-09 Thread Michel Dänzer
On Mit, 2002-10-09 at 05:34, Nicholas Leippe wrote: On Tuesday 08 October 2002 08:30 am, you wrote: Hi, I was quite interested to see this in the changelog of the latest Quake3 point release: - SMP support in the renderer. Detects CPU count, r_smp 1 default if available. (thanks

[Dri-devel] r200WaitForFrameCompletion: drmRadeonIrqWait: -16

2002-10-09 Thread Fabrice Bellet
Hello, I have regular crashes with the r200 driver, when running more than one GL app. I produced some logs, with drm debug enabled, and R200_DEBUG=sanity. The first program to be started is flightgear : http://www.creatis.insa-lyon.fr/~bellet/r200/fgfs.log.gz Everything is fine until I

Re: [Dri-devel] Quake3 1.32, r_smp 1, mga (G550) error

2002-10-09 Thread Adam K Kirchhoff
I'm getting something similar with the r200 driver... With +set r_smp 1, quake3 crashes with: Loading vm file vm/cgame.qvm. VM file cgame compiled to 786818 bytes of code cgame loaded in 5380768 bytes on the hunk drmCommandWrite: -22 drmRadeonCmdBuffer: -22 X is still usable, and isn't locked

Re: [Dri-devel] r200WaitForFrameCompletion: drmRadeonIrqWait: -16

2002-10-09 Thread Michel Dänzer
On Don, 2002-10-10 at 00:06, Fabrice Bellet wrote: I have regular crashes with the r200 driver, when running more than one GL app. I produced some logs, with drm debug enabled, and R200_DEBUG=sanity. The first program to be started is flightgear :

Re: [Dri-devel] Mesa 4.1 branch

2002-10-09 Thread Brian Paul
Brian Paul wrote: I've created a new DRI branch: mesa-4-1-branch I'm in the process of porting all the DRI drivers to the new Mesa 4.1 code. I'll be checking in changes soon, but don't expect anything to run or even compile. I'll post again when I think it's usable. OK, it's compiling

[Dri-devel] ANNOUNCEMENT: texmem-0-0-1 branch and what it means for you!

2002-10-09 Thread Ian Romanick
I have recently created and commited the first batch of code to the texmem-0-0-1 branch. The purpose of this branch is to refactor the client-side texture management code to a single place and port all (or nearly all) drivers to use that code. The new texture management code is in

[Dri-devel] Q3 PR 1.32 DRI/ATI SMP

2002-10-09 Thread Csan
Hi there, Is the any hope for us, ATI users to be able to enjoy the new SMP'ed PR also with ATI (ATI 7500 here)? I would desperately need the multithreaded functionality. What are the chances that we, ATI users will also be able to enjoy that feature? How could I help (not being a developer)?

Re: [Dri-devel] Mesa 4.1 branch

2002-10-09 Thread Michel Dänzer
On Don, 2002-10-10 at 00:42, Brian Paul wrote: Brian Paul wrote: I've created a new DRI branch: mesa-4-1-branch I'm in the process of porting all the DRI drivers to the new Mesa 4.1 code. I'll be checking in changes soon, but don't expect anything to run or even compile. I'll post

Re: [Dri-devel] Mesa 4.1 branch

2002-10-09 Thread Brian Paul
Michel Dänzer wrote: On Don, 2002-10-10 at 00:42, Brian Paul wrote: Brian Paul wrote: I've created a new DRI branch: mesa-4-1-branch I'm in the process of porting all the DRI drivers to the new Mesa 4.1 code. I'll be checking in changes soon, but don't expect anything to run or even compile.

Re: [Dri-devel] r200WaitForFrameCompletion: drmRadeonIrqWait: -16

2002-10-09 Thread Fabrice Bellet
On Thu, Oct 10, 2002 at 12:33:59AM +0200, Michel Dänzer wrote: What date is the DRM source you're using from? I updated my dri HEAD cvs tree two hours ago, and I rebuilt the drm module too. Oct 10 00:53:32 dhcp7 kernel: [drm] Debug messages ON Oct 10 00:53:32 dhcp7 kernel: [drm] AGP 0.99 on

Re: [Dri-devel] Mesa 4.1 branch

2002-10-09 Thread Brian Paul
Michel Dänzer wrote: On Don, 2002-10-10 at 01:31, Brian Paul wrote: I missed one check-in. The gl.h file needed updating. Try again. Builds now, thanks. I only get direct rendering with the libGL from the branch, this happens with the one from the trunk: daenzer@tibook

Re: [Dri-devel] r200WaitForFrameCompletion: drmRadeonIrqWait: -16

2002-10-09 Thread Michel Dänzer
On Don, 2002-10-10 at 01:42, Fabrice Bellet wrote: On Thu, Oct 10, 2002 at 12:33:59AM +0200, Michel Dänzer wrote: What date is the DRM source you're using from? I updated my dri HEAD cvs tree two hours ago, and I rebuilt the drm module too. [...] Does the interrupt count for the

Re: [Dri-devel] Mesa 4.1 branch

2002-10-09 Thread Michel Dänzer
On Don, 2002-10-10 at 02:36, Brian Paul wrote: Michel Dänzer wrote: On Don, 2002-10-10 at 01:31, Brian Paul wrote: I only get direct rendering with the libGL from the branch, this happens with the one from the trunk: [...] Fixed. Do another CVS update of Mesa and the DRI. CVS

[Dri-devel] problems with mga driver

2002-10-09 Thread Mihai Ganea
Hi, Having a glEnd without a glBegin crashes the driver with: t_imm_api.c:316: _tnl_end: Assertion `ctx-Driver.NeedFlush 0x1' failed. The video driver used is dri mga build 20020910 on a Matrox G400 16Mb. Here is a stupid program I wrote to demonstrate this: #include GL/glut.h void