[Dri-devel] 2.4.19-rc1 broke i815 agp support?

2002-06-24 Thread Slava Polyakov
I got a radeon, after upgrading to 2.4.19-rc1 I can't get direct hardware glx to work, no matter what I try I only get indirect rendering with the tcl branch. Did anyone else try rc1 with radeon? --- Sponsored by: ThinkGeek at http://www.Thin

[Dri-devel] Website comments

2002-06-24 Thread Smitty
From: Keith Whitwell <[EMAIL PROTECTED]> > - There's no easy link to the sourceforge projects page. yes and add the hosted by SF pic below (with some space) redline2 (finishes off the menu frame nicely) - The 'status' page has disappeared > change Hardware to Status in the menu frame. (makes

Re: [Dri-devel] How to trace switching to software rendering

2002-06-24 Thread Michel Dänzer
On Sat, 2002-06-22 at 18:31, Michael Schlueter wrote: > > thanks for your fast answer. > > Am Sam, 2002-06-22 um 00.00 schrieb Brian Paul: > > If you search the code, you'll find where we set these flags by > > calling mgaFallback() (via the FALLBACK() macro). You could put > > a printf in ther

[Dri-devel] Website

2002-06-24 Thread Ian Molton
Hi. Well, thanks for your comments. Just to lay some fears / concerns to rest... 1) It isnt done yet! :) 2) I have yet to add text nav to the main page 3) The status page is going to disappear permanently, to be merged with the hardware page. All will becoime clear ;-) (and things that arent ha

RE: [Dri-devel] Website [update!] -> frames colour

2002-06-24 Thread Smitty
Also, the frames need a bgcolor in the body. This is a pet peeve of mine, since I have my default background set to gray. Well if I can see them then I can grab them and resize them. I can also see this line in the old / original site? Liam it depends ---

Re: [Dri-devel] Re: [Dri-users] Visual artifacts... heavy

2002-06-24 Thread Michel Dänzer
On Mon, 2002-06-24 at 21:41, Zilvinas Valinskas wrote: > On Mon, Jun 24, 2002 at 09:34:39PM +0200, Willy Gardiol wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > > > Hi to everybody > > > > I have an ATI Rage128 16mb asnd i suffer strange visual artifacts in games > > like

Re: [Dri-devel] ATI Radeon 7500 Performance Issues

2002-06-24 Thread Michel Dänzer
On Sat, 2002-06-22 at 14:30, [EMAIL PROTECTED] wrote: > Michel =?ISO-8859-1?Q?D=E4nzer?= writes: > > On Thu, 2002-06-20 at 18:43, [EMAIL PROTECTED] wrote: > > > =?ISO-8859-1?Q?D=E4nzer?= writes: > > > ed, 2002-06-19 at 16:59, Adam K Kirchhoff wrote: > > > > > > 19 Jun 2002, Michel [ISO-88

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-24 Thread Keith Whitwell
Michel Dänzer wrote: > On Thu, 2002-06-13 at 17:00, Keith Whitwell wrote: > >>Steven Paul Lilly wrote: >> >>>I thought I would add my vote to the whole debate about what to do with the >>>mailing lists and SFBT. I would like both lists to continue and for their >>>proper uses to be enforced. I am

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-24 Thread Michel Dänzer
On Thu, 2002-06-13 at 17:00, Keith Whitwell wrote: > Steven Paul Lilly wrote: > > I thought I would add my vote to the whole debate about what to do with the > > mailing lists and SFBT. I would like both lists to continue and for their > > proper uses to be enforced. I am not a developer or even a

[Dri-devel] Fixed binaries on SF

2002-06-24 Thread José Fonseca
As some of you already noticed, fixed binaries - i.e, including libdri.a -, are now available on SF. When [and if] the binary compatability of libdri.a is restored, let me know and I'll restore the things as they were. José Fonseca --- Spon

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Jens Owen
Keith Whitwell wrote: > Jens Owen wrote: > >> >> >> Keith Whitwell wrote: >> >>> [EMAIL PROTECTED] wrote: >>> Jens - > Can you try with the old libdri.a, but the new libdrm.a. That's > where I > would expect the dependency for the new drmCommand interface to be >

Re: [Dri-devel] Why so difference between root and non root?

2002-06-24 Thread Michel Dänzer
On Mon, 2002-06-24 at 22:46, Willy Gardiol wrote: > > I feel big differences between playng games as root and as non root > > i have put the "mode 666" in the dri section in the xfree config file, i have > dri enabled both as root and as non root. > > glxgears says: > > as root 770 fps > as n

[Dri-devel] Why so difference between root and non root?

2002-06-24 Thread Willy Gardiol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I feel big differences between playng games as root and as non root i have put the "mode 666" in the dri section in the xfree config file, i have dri enabled both as root and as non root. glxgears says: as root 770 fps as non root 700 fps and ga

Re: [Dri-users] Re: [Dri-devel] Explanation about glxinfo

2002-06-24 Thread Brian Paul
Willy Gardiol wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Thanks, > whats is the difference between DirectColor and TrueColor? I have never heared > about DirectColor... TrueColor uses an immutable colormap (it can't be changed). With DirectColor each of the red, green and

Re: [Dri-users] Re: [Dri-devel] Explanation about glxinfo

2002-06-24 Thread Willy Gardiol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks, whats is the difference between DirectColor and TrueColor? I have never heared about DirectColor... But if you have a powerfull processor, couldnt be quicker to implement some buffers via software if you have a not-so-powerfull 3d hardware

[Dri-devel] Re: Radeon SourceForge d/l binaries (the ones everyones bitching about)

2002-06-24 Thread Konstantin Lepikhov
Hi Smitty! Monday 24, at 12:50:03 PM you wrote: > Well after beeing told to upgrade to XF4.2 from XF4.1 I did so: > > So XF4.2 Indirect rendering > install the latest / last binary package from TG > XF4.2 with direct rendering (no TCL) > compile (not install) the latest binary package (20020623

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Keith Whitwell
Jens Owen wrote: > > > Keith Whitwell wrote: > >> [EMAIL PROTECTED] wrote: >> >>> Jens - >>> >>> Can you try with the old libdri.a, but the new libdrm.a. That's where I would expect the dependency for the new drmCommand interface to be resolved. >>> >>> But that's exa

Re: [Dri-devel] Explanation about glxinfo

2002-06-24 Thread Brian Paul
Willy Gardiol wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > Hi! > could someone help me understand what the output of glxinfo means? > > here it is: > > (i snip what i understand) >visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav > id dep cl sp sz l

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Keith Whitwell
Jens Owen wrote: > > > José Fonseca wrote: > >> On Mon, Jun 24, 2002 at 07:19:35PM +0100, [EMAIL PROTECTED] wrote: >> >>> Hi all, >>> >>> Well, experimenting with my own build suggests that if you include >>> >>> /usr/X11R6/lib/modules/extensions/libdri.a >>> >>> in the binary packages, everyth

[Dri-devel] Radeon SourceForge d/l binaries (the ones everyones bitching about)

2002-06-24 Thread Smitty
Well after beeing told to upgrade to XF4.2 from XF4.1 I did so: So XF4.2 Indirect rendering install the latest / last binary package from TG XF4.2 with direct rendering (no TCL) compile (not install) the latest binary package (20020623) from SF copy every file to its proper location except radeon

[Dri-devel] Re: [Dri-users] Explanation about glxinfo

2002-06-24 Thread Zilvinas Valinskas
On Mon, Jun 24, 2002 at 09:37:18PM +0200, Willy Gardiol wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > Hi! > could someone help me understand what the output of glxinfo means? > > here it is: > > (i snip what i understand) >visual x bf lv rg d st colorbuffer ax dp st

[Dri-devel] Re: [Dri-users] Visual artifacts... heavy

2002-06-24 Thread Zilvinas Valinskas
On Mon, Jun 24, 2002 at 09:34:39PM +0200, Willy Gardiol wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Hi to everybody > > I have an ATI Rage128 16mb asnd i suffer strange visual artifacts in games > like Soldier Of Fortunes and Return To Castle Wolfstein: i can see trhough >

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Jens Owen
Keith Whitwell wrote: > [EMAIL PROTECTED] wrote: > >> Jens - >> >> >>> Can you try with the old libdri.a, but the new libdrm.a. That's where I >>> would expect the dependency for the new drmCommand interface to be >>> resolved. >>> >> >> But that's exactly what the SF binary packages give you

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Jens Owen
José Fonseca wrote: > On Mon, Jun 24, 2002 at 07:19:35PM +0100, [EMAIL PROTECTED] wrote: > >> Hi all, >> >> Well, experimenting with my own build suggests that if you include >> >> /usr/X11R6/lib/modules/extensions/libdri.a >> >> in the binary packages, everything works fine again. >> >> ie. r

[Dri-devel] Explanation about glxinfo

2002-06-24 Thread Willy Gardiol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! could someone help me understand what the output of glxinfo means? here it is: (i snip what i understand) visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Keith Whitwell
[EMAIL PROTECTED] wrote: > Jens - > > >>Can you try with the old libdri.a, but the new libdrm.a. That's where I >>would expect the dependency for the new drmCommand interface to be >>resolved. >> > > But that's exactly what the SF binary packages give you - they give > you a new libdrm.a as a

[Dri-devel] Visual artifacts... heavy

2002-06-24 Thread Willy Gardiol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi to everybody I have an ATI Rage128 16mb asnd i suffer strange visual artifacts in games like Soldier Of Fortunes and Return To Castle Wolfstein: i can see trhough walls ! This is not too bad because i can see enemies before they can spot me, bu

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread José Fonseca
On Mon, Jun 24, 2002 at 07:19:35PM +0100, [EMAIL PROTECTED] wrote: >Hi all, > >Well, experimenting with my own build suggests that if you include > >/usr/X11R6/lib/modules/extensions/libdri.a > >in the binary packages, everything works fine again. > >ie. radeon works if you install the following o

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread ahg
Jens - > Can you try with the old libdri.a, but the new libdrm.a. That's where I > would expect the dependency for the new drmCommand interface to be > resolved. But that's exactly what the SF binary packages give you - they give you a new libdrm.a as a matter of course, but not libdri.a. Upd

Re: [Dri-devel] Re: Re: website. (Jens Owen)

2002-06-24 Thread Smitty
On Sun, 23 Jun 2002 22:52:09 +0100 Keith Whitwell <[EMAIL PROTECTED]> wrote: > Smitty wrote: > >>>I want to get started putting up the new site, but no-one has told me > >>>how to access the webspace... > >>> > >>>I've given my sourceforge details and been added to the project... > >>> > >>Ian, >

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Jens Owen
[EMAIL PROTECTED] wrote: > Hi all, > > Well, experimenting with my own build suggests that if you include > > /usr/X11R6/lib/modules/extensions/libdri.a > > in the binary packages, everything works fine again. > > ie. radeon works if you install the following on top of a standard > XFree86

Re: [Dri-devel] SF binaries still broken

2002-06-24 Thread Michael Schlueter
Am Mon, 2002-06-24 um 20.00 schrieb Michel Dänzer: > On Mon, 2002-06-24 at 18:21, Michael Schlueter wrote: > > Am Mon, 2002-06-24 um 16.03 schrieb José Fonseca: > > > On Mon, Jun 24, 2002 at 01:52:06PM +0100, [EMAIL PROTECTED] wrote: > > > > > > > >> In http://dri.sf.net/snapshots/cf are binaries

Re: [Dri-devel] radeon_dri.c glitch

2002-06-24 Thread Keith Whitwell
Michel Dänzer wrote: > This is a typo, right? > > > > > > > Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c > === > RCS file: /cvsroot/dri/xc/xc

Re: [Dri-devel] fix for broken SF binaries

2002-06-24 Thread Keith Whitwell
[EMAIL PROTECTED] wrote: > Hi all, > > Well, experimenting with my own build suggests that if you include > > /usr/X11R6/lib/modules/extensions/libdri.a > > in the binary packages, everything works fine again. > > ie. radeon works if you install the following on top of a standard > XFree86 4.2

[Dri-devel] radeon_dri.c glitch

2002-06-24 Thread Michel Dänzer
This is a typo, right? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c

[Dri-devel] fix for broken SF binaries

2002-06-24 Thread ahg
Hi all, Well, experimenting with my own build suggests that if you include /usr/X11R6/lib/modules/extensions/libdri.a in the binary packages, everything works fine again. ie. radeon works if you install the following on top of a standard XFree86 4.2 distribution: drm kernel module /usr/X11R6/

Re: [Dri-devel] SF binaries still broken

2002-06-24 Thread Michel Dänzer
On Mon, 2002-06-24 at 18:21, Michael Schlueter wrote: > Am Mon, 2002-06-24 um 16.03 schrieb José Fonseca: > > On Mon, Jun 24, 2002 at 01:52:06PM +0100, [EMAIL PROTECTED] wrote: > > > > > >> In http://dri.sf.net/snapshots/cf are binaries produced by the > > >> SourceForge compiler farm. These were

RE: [Dri-devel] Website [update!]

2002-06-24 Thread Leif Delgass
On Mon, 24 Jun 2002, Alexander Stohr wrote: > The previous design had some headers and footers, i dont > think they are required any more to help if the menu bar > grafics didnt load, but for the sake of e.g. pure textmode > browsers without frames they are still helpful. The header/footer navig

RE: [Dri-devel] Website [update!]

2002-06-24 Thread Alexander Stohr
Hardware -> "wibble" whatever this is. DRI Logo doesnt represent a link to "home". it should be for convenience (other highly important things already mentioned by others.) for sake of niceness the sourceforge.net link with logo is missing. The previous design had some headers and footers, i d

Re: [Dri-devel] R200 kernel interfaces

2002-06-24 Thread Ian Romanick
On Tue, Jun 18, 2002 at 12:09:02AM +0100, José Fonseca wrote: > On 2002.06.17 23:19 Keith Whitwell wrote: > > > >> > >> We could overcome the GLX difficulties in the same way we do now in > >> libGL with the direct rendering. > >> > >> But I still don't understand why vertex arrays would be su

Re: [Dri-devel] tuxkart, and bug reports..

2002-06-24 Thread Al Tobey
If somebody wants to provide a server, I'd be happy to set up Bugzilla for DRI. I have it running here at work and it's not that bad. If I end up with some extra time, I might be able to bring it up on my machines at home, but that's not a reliable enough connection for general use. Email notif

Re: [Dri-devel] Website [update!]

2002-06-24 Thread Jens Owen
Ian Molton wrote: > Well, I've backed up the old website (except for the huge snapshots > folder. > > I've also put the shell of the new site up. go to > http://dri.sourceforge.net/new_site/ to see it. > > I'm awaiting some charts and a couple of pages from Liam, which look to > become excell

Re: [Dri-devel] SF binaries still broken

2002-06-24 Thread Michael Schlueter
Am Mon, 2002-06-24 um 16.03 schrieb José Fonseca: > On Mon, Jun 24, 2002 at 01:52:06PM +0100, [EMAIL PROTECTED] wrote: > > > >> In http://dri.sf.net/snapshots/cf are binaries produced by the > >> SourceForge compiler farm. These were intended to replace the ones > >> made on my workstation but I n

Re: [Dri-devel] Website [update!]

2002-06-24 Thread Keith Whitwell
Ian Molton wrote: > Well, I've backed up the old website (except for the huge snapshots > folder. > > I've also put the shell of the new site up. go to > http://dri.sourceforge.net/new_site/ to see it. > It looks like it's got a way to go before it incorporates all of the content from the old

Re: [Dri-devel] tuxkart, and bug reports..

2002-06-24 Thread Ian Romanick
On Wed, Jun 12, 2002 at 06:42:06PM +0100, Keith Whitwell wrote: > I'm just in general not a big fan of the bug tracker. I've got a bunch of > bugs that I can choose from at any time without having to go through some web > form that requires me to log in and wait for slow queries. It doesn't g

[Dri-devel] Website [update!]

2002-06-24 Thread Ian Molton
Well, I've backed up the old website (except for the huge snapshots folder. I've also put the shell of the new site up. go to http://dri.sourceforge.net/new_site/ to see it. I'm awaiting some charts and a couple of pages from Liam, which look to become excellent references, and I have yet to hoo

Re: [Dri-devel] TCL lockups with Tribes 2

2002-06-24 Thread Al Tobey
If there is a windows machine on the network, you can still access your box a couple ways. One is by using telnet, although it is very insecure. Next is to download either "putty" or "teraterm/ssh" (google will find these for you quickly) and use them to access your machine via secure shell. A

Re: [Dri-devel] SF binaries still broken

2002-06-24 Thread Keith Whitwell
José Fonseca wrote: > On Mon, Jun 24, 2002 at 01:52:06PM +0100, [EMAIL PROTECTED] wrote: > >> >>> In http://dri.sf.net/snapshots/cf are binaries produced by the >>> SourceForge compiler farm. These were intended to replace the ones >>> made on my workstation but I never actualy did that because I

Re: [Dri-devel] SF binaries still broken

2002-06-24 Thread José Fonseca
On Mon, Jun 24, 2002 at 01:52:06PM +0100, [EMAIL PROTECTED] wrote: > >> In http://dri.sf.net/snapshots/cf are binaries produced by the >> SourceForge compiler farm. These were intended to replace the ones >> made on my workstation but I never actualy did that because I wasn't >> so confident with

Re: [Dri-devel] Re: radeon cvs problem ([email protected]) - binary packages

2002-06-24 Thread José Fonseca
On Sun, Jun 23, 2002 at 09:50:32AM -0700, Smitty wrote: > > ... > >On a side note: >radeon_dri.so is 5.2MB in the SF d/l and >radeon_dri.so is 1.8MB in the TG d/l. >Any explanation? > Debugging info I suppose. The ones in SF have it. José Fonseca --

Re: [Dri-devel] Re: agpgart, nFORCE (Al Tobey)

2002-06-24 Thread Al Tobey
Busy weekend .. I haven't been able to try much with the driver yet. I have tried "agp_try_unsupported=1" with insmod with no success so far. I got 2.4.22-dj2 to compile finally, so as soon as I get a couple hours, I'll try all of the available drivers and see what happens. If it fails complete

RE: [Dri-devel] Re: Compilation

2002-06-24 Thread Alexander Stohr
> Hello Alexander! > > No change to get this going on "your partner" boards? > Even with flashed BIOS? > > I can get may hands on a 8500LE on top of my dual Athlon > 1900+ MP/XP for > testing. > > Thanks, > Dieter The partner boards do have individual board features which aren't tested

Re: [Dri-devel] Re: Compilation

2002-06-24 Thread Stefan Lange
Dieter Nützel wrote: > On Monday 24 June 2002 13:09, Alexander Stohr wrote: > >>Or you are try out the current closed source drivers >>for X11 and the ATI FireGL 8700/8800 - they do run >>on the "BUILT BY ATI" Radeon 8500 boards as well. >>The board indicates this compatibility by a PCI >>Subvend

Re: [Dri-devel] Re: Compilation

2002-06-24 Thread Dieter Nützel
On Monday 24 June 2002 13:09, Alexander Stohr wrote: > Or you are try out the current closed source drivers > for X11 and the ATI FireGL 8700/8800 - they do run > on the "BUILT BY ATI" Radeon 8500 boards as well. > The board indicates this compatibility by a PCI > Subvendor ID of 0x1002 or ATI. H

RE: [Dri-devel] SF binaries still broken

2002-06-24 Thread ahg
> In http://dri.sf.net/snapshots/cf are binaries produced by the > SourceForge compiler farm. These were intended to replace the ones > made on my workstation but I never actualy did that because I wasn't > so confident with all the hacks that were necessary to get them to > compile. Could you p

RE: [Dri-devel] Re: Compilation

2002-06-24 Thread Alexander Stohr
Or you are try out the current closed source drivers for X11 and the ATI FireGL 8700/8800 - they do run on the "BUILT BY ATI" Radeon 8500 boards as well. The board indicates this compatibility by a PCI Subvendor ID of 0x1002 or ATI. > -Original Message- > From: Mike A. Harris [mailto:[EM

Re: [Dri-devel] SF binaries still broken

2002-06-24 Thread José Fonseca
On Mon, Jun 24, 2002 at 07:13:59AM +0100, [EMAIL PROTECTED] wrote: >Dear Jose, > >> I've disabled the merge with the XFree86 4.2.0 code to see if that >> helps and fired up a new build. Please check if the next binaries >> are ok. > >Sorry to report that the latest SF binaries (well, at least >rad