[Dri-devel] DRM pci ids

2004-04-18 Thread Dave Airlie
Okay I've come up with a method for generating the pci ids stuff for the DRM for Linux and BSD, put a txt file in shared or the format [cardname] vendid devid "namestring" have two scripts in the scripts directory ones to create a linux drm_pciids.h file of the format #define cardname_PCI_IDS \

Re: [Dri-devel] RE: radeon t_vertex conversion

2004-04-18 Thread Keith Whitwell
Andreas Stenglein wrote: sorry.. I missed to set tcl_mode=0, so the programs were running in HW-TCL mode. After setting tcl_mode to 0, glxgears and quake3 didnt work as expected. Ah gack, my r200 changes haven't been tested for similar reasons... Keith -

Re: [Dri-devel] RE: radeon t_vertex conversion (was: R200 t_vertex conversion)

2004-04-18 Thread Michel Dänzer
On Mon, 2004-04-19 at 00:29, Andreas Stenglein wrote: > > After setting tcl_mode to 0, glxgears and quake3 didnt work as expected. glxgears looks like http://penguinppc.org/~daenzer/DRI/glxgears.png here; if I press the cursor keys, the inner colour changes, but not the geometry. Is this what you

Re: [Dri-devel] [PATCH] Convert r128 driver in linux kernel 2.6 to use userland firmware loading

2004-04-18 Thread Ryan Underwood
On Sun, Apr 18, 2004 at 09:20:00AM +0100, Alan Cox wrote: > > Otherwise, it could simply be a configuration list that is parsed by the > > device, or a memory initialization image, or a dispatch table, or > > something similar, and rejecting such things on the basis that they are > > *suspected*

[Dri-devel] RE: radeon t_vertex conversion (was: R200 t_vertex conversion)

2004-04-18 Thread Andreas Stenglein
sorry.. I missed to set tcl_mode=0, so the programs were running in HW-TCL mode. After setting tcl_mode to 0, glxgears and quake3 didnt work as expected. best regards, Andreas --- This SF.Net email is sponsored by: IBM Linux Tutorials Free L

[Dri-devel] Radeon t_vertex conversion (was: R200 t_vertex conversion)

2004-04-18 Thread Andreas Stenglein
I tried to merge the r200 patch to the radeon driver. Here is a snapshot. (hopefully I didn't miss something while sorting out the r200 stuff from the diff.) I tested: glxgears works, quake3 works, ut2004demo works (at least to a certain extend) progs/tests/projtex doesn't work as it should, yuvr

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-18 Thread Alan Hourihane
On Sun, Apr 18, 2004 at 01:33:41PM +0200, Michel Dänzer wrote: > On Sun, 2004-04-18 at 04:19, Donnie Berkholz wrote: > > On Sat, 2004-04-17 at 07:54, Alan Hourihane wrote: > > > On Sat, Apr 17, 2004 at 01:18:49AM +0200, Michel Dänzer wrote: > > > > On Sat, 2004-04-17 at 00:00, Alan Hourihane wrote:

Re: [Dri-devel] Makefiles in the drm module

2004-04-18 Thread Felix Kühling
On Sun, 18 Apr 2004 01:53:40 +0200 Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Wed, 2004-04-14 at 16:19, Keith Whitwell wrote: > > Michel Dänzer wrote: > > > Does anything speak against repo-moving Makefile.{bsd,linux} to > > > Makefile? > > > > I can't think of any reason not to. > > Turns o

Re: [Dri-devel] [r200] Viewperf-7.1.1 numbers - Not so good.

2004-04-18 Thread Dieter Nützel
Am Montag, 5. April 2004 19:05 schrieb Dieter Nützel: > dual Athlon MP 1900+ > MSI K7D Master-L (AMD 760 MPX) > 1 GB DDR266, CL2 (2x 512 MB) > Radeon 8500QL, 64 MB > Linux 2.6.4-44.9 (SuSE 9.0.42 with 2.6.5-rc-mm stuff) > Latest DRI CVS trunk (Mesa-6.1) > > SMP in Mesa isn't working, today. (Since

Re: [Dri-devel] [PATCH] R200 t_vertex conversion

2004-04-18 Thread Keith Whitwell
Keith Whitwell wrote: Ian Romanick wrote: This is what I have done so far to convert the R200 driver to use t_vertex. It is only a conversion for SW TCL, and it's not quite complete. I've managed to clean up all the crashes that I could find, but I've only tested with gears, geartrain, and tu

Re: [Dri-devel] [PATCH] Convert r128 driver in linux kernel 2.6 to use userland firmware loading

2004-04-18 Thread Alan Cox
On Sul, 2004-04-18 at 07:52, Ryan Underwood wrote: > So your advisor is saying that such a work is undistributable under the > GPL, or are they saying that it is not distributable at all? They are saying that in their reading of the law it would be better if the firmware was kept seperate. Lawyers

Re: [Dri-devel] Questions about current status of DRI

2004-04-18 Thread Michel Dänzer
On Sun, 2004-04-18 at 04:55, Vladimir Dergachev wrote: > On Sun, 18 Apr 2004, Michel [ISO-8859-1] Dnzer wrote: > > > On Sun, 2004-04-18 at 03:19, Vladimir Dergachev wrote: > > > > > > 3. Can anyone tell me what changes are required in order to enable > > > "idle" DRI for R300 and above ? (I

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-18 Thread Michel Dänzer
On Sun, 2004-04-18 at 04:19, Donnie Berkholz wrote: > On Sat, 2004-04-17 at 07:54, Alan Hourihane wrote: > > On Sat, Apr 17, 2004 at 01:18:49AM +0200, Michel DÃnzer wrote: > > > On Sat, 2004-04-17 at 00:00, Alan Hourihane wrote: > > > > > > > > I could merge in XFree86 4.3.99.902 which is before t