Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch:bsd-3-0-0-branch)

2002-06-26 Thread Eric Anholt
On Wed, 2002-06-26 at 23:50, Jens Owen wrote: > For the drivers you've ported to your OS independent templates (radeon, > r128 and mga), it looks like the *_drv.c and Makefile support are all > that's left in the OS directories. If you can get these out of there, > even by adding a few OS ifde

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: bsd-3-0-0-branch)

2002-06-26 Thread Eric Anholt
On Wed, 2002-06-26 at 23:12, Jens Owen wrote: > Eric Anholt wrote: > > > > Log message: > > The drmCommand interface was passing a size to DRM_IOR() and friends, > > when DRM_IOR was expecting a type, so on BSD only an int was copied in/out of > > the kernel. Make drmCommand use new DRM_I

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: bsd-3-0-0-branch)

2002-06-26 Thread Jens Owen
Eric Anholt wrote: >>Log message: >> Include protection against ioctl() definition only in the __FreeBSD__ and >> XFree86Server case. These two drm.h's probably should be shared. >> > > With this commit radeon, r128, and mga are all working on FreeBSD and > Linux. Haven't tested tdfx, but I

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: bsd-3-0-0-branch)

2002-06-26 Thread Jens Owen
Eric Anholt wrote: > Log message: > The drmCommand interface was passing a size to DRM_IOR() and friends, > when DRM_IOR was expecting a type, so on BSD only an int was copied in/out of > the kernel. Make drmCommand use new DRM_IOC(), which expects a size. Good catch! I'm surprised this

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: bsd-3-0-0-branch)

2002-06-26 Thread Eric Anholt
> Log message: > Include protection against ioctl() definition only in the __FreeBSD__ and > XFree86Server case. These two drm.h's probably should be shared. With this commit radeon, r128, and mga are all working on FreeBSD and Linux. Haven't tested tdfx, but I have no reason to not expect

[Dri-devel] Re: S3 VIRGE DRI in CVS now

2002-06-26 Thread John J. Tobin
On Wed, 2002-06-26 at 17:43, Massimiliano Lingua wrote: > On Thu, 2002-06-27 at 00:24, John J. Tobin wrote: > > > Alright, I have it built, took long enough on my K6-2 laptop but I have > > having some problems. Glxinfo reports that there is direct rendering and > > everything but if I try to run

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

2002-06-26 Thread Ville Syrjälä
On Wed, Jun 26, 2002 at 04:43:35PM -0600, Brian Paul wrote: > Without looking at the code, my guess is that the GL_DECAL env mode > with an RGBA texture probably isn't implemented in hardware. Hardware > from that era often had limitations that prevented some combinations > of texture env modes a

RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Alexander Stohr
some of the current desktop managers has those "dial home" feature with the fault handler built in. each crash could get sent to the development team if the user likes it. Maybe improved crash logging should get an integral feature of X11 on general platforms (of course embedded folks wont like

RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Al Tobey
I'll first get a nice easy script working. If it proves a hit with developers, I'll script out a gdb backtrace on the X server, just in case it crashed. This might require a small X client that keeps trying to update itself (say, every second), which triggers the backtrace when it fails. Just a

Re: [Dri-devel] Parhelia vs. Radeon 8500

2002-06-26 Thread Dieter Nützel
On Thursday 27 June 2002 00:18, José Fonseca wrote: > On Wed, Jun 26, 2002 at 11:22:16PM +0200, German Gomez Garcia wrote: > > Hello, I have some money to spend (finally!!!) so I'm thinking > >of replacing my old G400MAX for a new card, as I prefer open source, I > >have to choose between ATI

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Alan Hourihane
On Thu, Jun 27, 2002 at 12:48:30AM +0200, Massimiliano Lingua wrote: > On Wed, 2002-06-26 at 19:16, Alan Hourihane wrote: > > > > > It builds now, so could you 'cvs update' build, install, and check > > everything is working. > > I had some problem building it in mesa/src/drv/s3v > > In s3v_co

Re: [dbronaugh@linuxboxen.org: Re: [Dri-devel] Annouce: S3 Virge binary snapshots (Was: CVS Update: xc (branch: s3virge-0-0-1-branch))]

2002-06-26 Thread Alan Hourihane
O.k. I've just fixed this issue. Alan. On Wed, Jun 26, 2002 at 11:20:10PM +0100, José Fonseca wrote: > - Forwarded message from David Bronaugh <[EMAIL PROTECTED]> - > > Date: Wed, 26 Jun 2002 14:54:29 -0700 > From: David Bronaugh <[EMAIL PROTECTED]> > Subject: Re: [Dri-devel] Annouce: S

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 19:16, Alan Hourihane wrote: > > It builds now, so could you 'cvs update' build, install, and check > everything is working. I had some problem building it in mesa/src/drv/s3v In s3v_context.h (215) I have something like "drm_s3v_sarea_t". Where other drivers seems to hav

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

2002-06-26 Thread Brian Paul
Michael Schlueter wrote: > Hi Brian, > > sorry for disturb you again. > > Am Sam, 2002-06-22 um 00.00 schrieb Brian Paul: > >>Most of the DRI drivers have a per-context field called 'Fallback'. >>It's a bitmask which records various reasons why we need to fallback >>to software rendering. In t

[Dri-devel] Re: S3 VIRGE DRI in CVS now

2002-06-26 Thread Massimiliano Lingua
On Thu, 2002-06-27 at 00:24, John J. Tobin wrote: > Alright, I have it built, took long enough on my K6-2 laptop but I have > having some problems. Glxinfo reports that there is direct rendering and > everything but if I try to run glxgears the system hard locks. The specs > are: > Sager NP9800 l

[Dri-devel] Re: S3 VIRGE DRI in CVS now

2002-06-26 Thread John J. Tobin
On Tue, 2002-06-25 at 16:35, Massimiliano Lingua wrote: > On Tue, 2002-06-25 at 16:48, John J. Tobin wrote: > > > > > Is the Virge MX+ supported? This is the one that was commonly found in > > notebooks, as that is what I will be testing it out on. > > > Yep. That is the laptop on which I deve

[dbronaugh@linuxboxen.org: Re: [Dri-devel] Annouce: S3 Virge binary snapshots (Was: CVS Update: xc (branch: s3virge-0-0-1-branch))]

2002-06-26 Thread José Fonseca
- Forwarded message from David Bronaugh <[EMAIL PROTECTED]> - Date: Wed, 26 Jun 2002 14:54:29 -0700 From: David Bronaugh <[EMAIL PROTECTED]> Subject: Re: [Dri-devel] Annouce: S3 Virge binary snapshots (Was: CVS Update: xc (branch: s3virge-0-0-1-branch)) To: Jos Fonseca <[EMAIL PROTECTED]

Re: [Dri-devel] Parhelia vs. Radeon 8500

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 11:22:16PM +0200, German Gomez Garcia wrote: > Hello, I have some money to spend (finally!!!) so I'm thinking >of replacing my old G400MAX for a new card, as I prefer open source, I >have to choose between ATI and Matrox, and the optios (for me) are >the new Parhelia

[Dri-devel] Parhelia vs. Radeon 8500

2002-06-26 Thread German Gomez Garcia
Hello, I have some money to spend (finally!!!) so I'm thinking of replacing my old G400MAX for a new card, as I prefer open source, I have to choose between ATI and Matrox, and the optios (for me) are the new Parhelia 512 or the AIW Radeon 8500 DV, I'll buy whatever card works better under

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

2002-06-26 Thread Michael Schlueter
Hi Brian, sorry for disturb you again. Am Sam, 2002-06-22 um 00.00 schrieb Brian Paul: > Most of the DRI drivers have a per-context field called 'Fallback'. > It's a bitmask which records various reasons why we need to fallback > to software rendering. In the case of the mga (G400) driver you'l

[Dri-devel] Annouce: S3 Virge binary snapshots (Was: CVS Update: xc (branch: s3virge-0-0-1-branch))

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 08:56:04PM +0100, Alan Hourihane wrote: >On Wed, Jun 26, 2002 at 08:38:03PM +0100, José Fonseca wrote: >> On Wed, Jun 26, 2002 at 10:04:27AM -0700, Alan Hourihane wrote: >> > o.k. it's builds now, max needs to check it runs o.k. >> > >> >> ... >> >> Perhaps something was

Re: [Dri-devel] Re: Merging trunk changes into mach64 branch

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 04:22:07PM -0400, Leif Delgass wrote: >On Wed, 26 Jun 2002, Alan Hourihane wrote: > >> On Wed, Jun 26, 2002 at 07:44:14PM +0100, José Fonseca wrote: >> > Alan, hint? (Or "How have you just done now with the s3virge branch?") >> >> cvs update -j HEAD >> >> and resolve the

Re: [Dri-devel] Re: Merging trunk changes into mach64 branch

2002-06-26 Thread Leif Delgass
On Wed, 26 Jun 2002, Alan Hourihane wrote: > On Wed, Jun 26, 2002 at 07:44:14PM +0100, José Fonseca wrote: > > Alan, hint? (Or "How have you just done now with the s3virge branch?") > > cvs update -j HEAD > > and resolve the conflicts by hand. OK, I can do that. I guess it'll be about the sam

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: s3virge-0-0-1-branch)

2002-06-26 Thread Alan Hourihane
On Wed, Jun 26, 2002 at 08:38:03PM +0100, José Fonseca wrote: > On Wed, Jun 26, 2002 at 10:04:27AM -0700, Alan Hourihane wrote: > > o.k. it's builds now, max needs to check it runs o.k. > > > > I've tested and I still get errors when building it: > > gcc -c -O2 -ansi -Wall -Wpointer-arith -Wstr

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: s3virge-0-0-1-branch)

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 10:04:27AM -0700, Alan Hourihane wrote: > o.k. it's builds now, max needs to check it runs o.k. > I've tested and I still get errors when building it: gcc -c -O2 -ansi -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-extern

RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Sergey V. Udaltsov
Good boys! Can anyone invent the way to do the same thing with gdb? So on X crash one could get backtrace without remote debugging... Cheers, Sergey --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | S

[Dri-devel] Re: Merging trunk changes into mach64 branch

2002-06-26 Thread Alan Hourihane
On Wed, Jun 26, 2002 at 07:44:14PM +0100, José Fonseca wrote: > Alan, hint? (Or "How have you just done now with the s3virge branch?") cvs update -j HEAD and resolve the conflicts by hand. Alan. --- This sf.net email is sponsored by: Jabber

Re: [Dri-devel] RE: S3 VIRGE DRI in CVS now

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 08:51:18PM +0200, Massimiliano Lingua wrote: >On Wed, 2002-06-26 at 16:48, José Fonseca wrote: > > >> Are the ProSavage docs you have enough to get a good start on Savage4? > >their 3D engine is nearly identical. Er, I forgot, I got Savage4 docs >too from S3/VIA. I am defin

Re: [Dri-devel] RE: S3 VIRGE DRI in CVS now

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 16:48, José Fonseca wrote: > Are the ProSavage docs you have enough to get a good start on Savage4? their 3D engine is nearly identical. Er, I forgot, I got Savage4 docs too from S3/VIA. I am definetly the luckiest coder on Earth ; ) So on a Savage4 running my hack you wi

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 19:16, Alan Hourihane wrote: > > I'll try and give you a hand on this now. T H A N K S Be my guest in case you travel to Italy ; ) > It builds now, so could you 'cvs update' build, install, and check > everything is working. Ok. I am doing cvs update right now ; ) I w

[Dri-devel] Re: Merging trunk changes into mach64 branch

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 02:17:26PM -0400, Leif Delgass wrote: >On Wed, 26 Jun 2002, José Fonseca wrote: > [...] >> >> Yep. That's it. Basically one needs to checkout the trunk, tag it with >> the new mach64-0-0-5-branch, and then merge from the old branch (by >> doing cvs update -r mach64-0-0-4-b

[Dri-devel] Re: Merging trunk changes into mach64 branch

2002-06-26 Thread Leif Delgass
On Wed, 26 Jun 2002, José Fonseca wrote: > On Wed, Jun 26, 2002 at 01:52:00PM -0400, Leif Delgass wrote: > >On Wed, 26 Jun 2002, José Fonseca wrote: > > > >> On Wed, Jun 26, 2002 at 12:16:15PM -0400, Leif Delgass wrote: > >> [...] > >> >Jose, I think now would be a good time for us to merge the t

[Dri-devel] Re: Merging trunk changes into mach64 branch

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 01:52:00PM -0400, Leif Delgass wrote: >On Wed, 26 Jun 2002, José Fonseca wrote: > >> On Wed, Jun 26, 2002 at 12:16:15PM -0400, Leif Delgass wrote: >> [...] >> >Jose, I think now would be a good time for us to merge the trunk into a >> >new Mach64 branch. Brian released Me

[Dri-devel] Merging trunk changes into mach64 branch

2002-06-26 Thread Leif Delgass
On Wed, 26 Jun 2002, José Fonseca wrote: > On Wed, Jun 26, 2002 at 12:16:15PM -0400, Leif Delgass wrote: > [...] > >Jose, I think now would be a good time for us to merge the trunk into a > >new Mach64 branch. Brian released Mesa 4.0.3 and the trunk looks like > >it's been updated, and we need

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Alan Hourihane
On Wed, Jun 26, 2002 at 04:31:09PM +0100, Alan Hourihane wrote: > On Wed, Jun 26, 2002 at 03:59:06PM +0200, Massimiliano Lingua wrote: > > On Wed, 2002-06-26 at 15:52, Alan Hourihane wrote: > > > > > I'll do the merge now for you. > > > > > > Obviously this branch won't build at all until fixed

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: s3virge-0-0-1-branch)

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 12:16:15PM -0400, Leif Delgass wrote: [...] >Jose, I think now would be a good time for us to merge the trunk into a >new Mach64 branch. Brian released Mesa 4.0.3 and the trunk looks like >it's been updated, and we need to convert to drmCommand as well. Plus >there are

[Dri-devel] Re: Fixed binaries on SF

2002-06-26 Thread Konstantin Lepikhov
Hi Alexander! Wednesday 26, at 06:22:24 PM you wrote: > > he using 20020625 snapshot > > > > from XFree86.0.log > > ... > > (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:1:0:0), > > Permission denied > > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. > > ... > > Huh? Hi might

RE: [Dri-devel] Re: Fixed binaries on SF

2002-06-26 Thread Alexander Stohr
> he using 20020625 snapshot > > from XFree86.0.log > ... > (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:1:0:0), > Permission denied > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. > ... Huh? Hi might try as root. If it works then something with per user file permissions or st

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch:s3virge-0-0-1-branch)

2002-06-26 Thread Leif Delgass
On Wed, 26 Jun 2002, José Fonseca wrote: > On Wed, Jun 26, 2002 at 07:07:00AM -0700, Alan Hourihane wrote: > > merge trunk into s3virge branch (probably won't build at all now). > > > > Needs fixing for drmCommand interface. > > > > Er.. I was just about to suggest to do the merge in a new b

[Dri-devel] Re: Fixed binaries on SF

2002-06-26 Thread Konstantin Lepikhov
Hi Jos?! Tuesday 25, at 09:48:20 AM you wrote: > On Tue, Jun 25, 2002 at 12:06:36PM +0400, Konstantin Lepikhov wrote: > >Hi Jos?! > > > >Monday 24, at 10:16:51 PM you wrote: > > > >>As some of you already noticed, fixed binaries - i.e, including libdri.a > >>-, are now available on SF. > >> >

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: s3virge-0-0-1-branch)

2002-06-26 Thread Alan Hourihane
On Wed, Jun 26, 2002 at 04:00:18PM +0100, José Fonseca wrote: > On Wed, Jun 26, 2002 at 07:07:00AM -0700, Alan Hourihane wrote: > > merge trunk into s3virge branch (probably won't build at all now). > > > > Needs fixing for drmCommand interface. > > > > Er.. I was just about to suggest to do the

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: r200-0-1-branch)

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 07:54:23AM -0700, Keith Whitwell wrote: >CVSROOT: /cvsroot/dri >Module name: xc >Repository:xc/xc/lib/GL/mesa/src/drv/r200/ >Changes by:keithw@usw-pr-cvs1. 02/06/26 07:54:23 > >Log message: > Turn depth testing on, remove debug, turn tcl off by default.

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: s3virge-0-0-1-branch)

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 07:07:00AM -0700, Alan Hourihane wrote: > merge trunk into s3virge branch (probably won't build at all now). > > Needs fixing for drmCommand interface. > Er.. I was just about to suggest to do the merge in a new branch (e.g., s3virge-0-0-2-branch) to avoid leave the s3

RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Alexander Stohr
i would prefer this DRI_DEBUG_DIR=/var/tmp/dri_debug_`date +%Y-%m-%d-%T` so that on sorted dir listings the most recent is always on top since this date is encoded "MSB first". (textual month locales wont sort that good at all.) another two things you might want to add: /sbin/lspci -vvv >$DRI

Re: [Dri-devel] RE: S3 VIRGE DRI in CVS now

2002-06-26 Thread José Fonseca
On Wed, Jun 26, 2002 at 03:39:08PM +0200, Massimiliano Lingua wrote: >On Wed, 2002-06-26 at 13:07, Alexander Stohr wrote: >> > A bit I had to study (laws + Savage4 docs). >> >> Savage4 docs??? >> can you tell me whats up with them now? > >I got ProSavage docs and BCI tech ref from VIA/S3 under ND

[Dri-devel] Re: S3 VIRGE DRI in CVS now

2002-06-26 Thread Massimiliano Lingua
>> Do you mean S3 Savage MX or is it a S3 virge MX??? >> Thanks, >> JrSky. S3 *** Virge *** MX. For Savage MX try utah. Or wait for us to code a driver ; ) Vale, - max --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM ev

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 15:52, Alan Hourihane wrote: > I'll do the merge now for you. > > Obviously this branch won't build at all until fixed up for the > new drmCommand stuff. I have been away a couple of months from active development. Where could I gather more infos about drmCommand? Is it ea

[Dri-devel] Re: Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 12:45, José Fonseca wrote: > > Max, is there any file related to i830 missing or outdated in the > s3virge branch? Or perhaps the i830 driver should be disabled on this > branch. There was a stale #if 0 in drm/kernel/drm.h. Fixed now. Could you please let me know if this i

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Alan Hourihane
On Wed, Jun 26, 2002 at 03:43:42PM +0200, Massimiliano Lingua wrote: > On Wed, 2002-06-26 at 12:54, Alan Hourihane wrote: > > I can do the trunk merge for you, if you want to fixup the code > > later. > > Ok. It would be very nice from you. What I am supposed to do after: > cvs update? So that co

[Dri-devel] RE: S3 VIRGE DRI in CVS now

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 13:07, Alexander Stohr wrote: > > A bit I had to study (laws + Savage4 docs). > > Savage4 docs??? > can you tell me whats up with them now? I got ProSavage docs and BCI tech ref from VIA/S3 under NDA. I have a very primitive Savage4 3D driver too (it paints just 3D tris - b

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 12:54, Alan Hourihane wrote: > I can do the trunk merge for you, if you want to fixup the code > later. Ok. It would be very nice from you. What I am supposed to do after: cvs update? So that code on my HD will get in sync with CVS? Thanks in advance, vale, - max -

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Massimiliano Lingua
On Wed, 2002-06-26 at 12:54, Alan Hourihane wrote: > Looks like the s3virge branch is lagging quite a bit behind the trunk. Yep. The branch was created in late March. > Max - you should bring in the current trunk code into your s3virge > branch and fixup for the new drmCommand interface. Ok. I

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2002-06-26 Thread Keith Whitwell
Michel Dänzer wrote: > On Wed, 2002-06-26 at 10:32, Keith Whitwell wrote: > >>CVSROOT: /cvsroot/dri >>Module name: xc >>Repository: xc/xc/lib/GL/mesa/src/drv/radeon/ >>Changes by: keithw@usw-pr-cvs1. 02/06/26 01:32:32 >> >>Log message: >> Fog correction >> > > Out of curiosity, wh

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2002-06-26 Thread Michel Dänzer
On Wed, 2002-06-26 at 10:32, Keith Whitwell wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/lib/GL/mesa/src/drv/radeon/ > Changes by: keithw@usw-pr-cvs1. 02/06/26 01:32:32 > > Log message: > Fog correction Out of curiosity, what was the problem? -- Earthli

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Alan Hourihane
Looks like the s3virge branch is lagging quite a bit behind the trunk. Max - you should bring in the current trunk code into your s3virge branch and fixup for the new drmCommand interface. Alan. On Wed, Jun 26, 2002 at 11:45:51AM +0100, José Fonseca wrote: > Last night the script tried to build

Re: [Dri-devel] Re: S3 VIRGE DRI in CVS now

2002-06-26 Thread roussel jerome
Massimiliano Lingua wrote: >On Tue, 2002-06-25 at 16:48, John J. Tobin wrote: > > > >>Is the Virge MX+ supported? This is the one that was commonly found in >>notebooks, as that is what I will be testing it out on. >> >> >> >Yep. That is the laptop on which I developed my driver on. so it

Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread Alan Hourihane
I can do the trunk merge for you, if you want to fixup the code later. Alan. On Wed, Jun 26, 2002 at 11:45:51AM +0100, José Fonseca wrote: > Last night the script tried to build the s3virge binary snapshot for the > first time, but it failed when building a file related with the i830 > driver: >

[Dri-devel] Failure to build the s3virge-0-0-1-branch

2002-06-26 Thread José Fonseca
Last night the script tried to build the s3virge binary snapshot for the first time, but it failed when building a file related with the i830 driver: gcc -O2 -ansi -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -pipe -g -fno-merge-constan

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

2002-06-26 Thread Nicolas Aspert
Slava Polyakov wrote: > > Nope... dmesg shows all the same with both kernels: > > [drm] AGP 0.99 on Intel i815 @ 0xd800 64MB > [drm] Initialized radeon 1.3.0 20020521 on minor 0 > Can you extract the agpgart bits from /var/log/messages (the drm is a different part) ? It should look like

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

2002-06-26 Thread Slava Polyakov
On June 26, 2002 02:29 am, Nicolas Aspert wrote: > Slava Polyakov wrote: > > 2.4.19-pre10: > > > > version: 0.99 > > bridge id: 0x11308086 > > agp_mode: 0x1f000207 > > aper_base: 0xd800 > > aper_size: 64 > > pg_total: 82176 > > pg_system: 82176 > > pg_used: 0 > > entry.key : 0 > > entry.key :

[Dri-devel] Save Big with steep declines in interest rates 0635WwjX2-556j-13

2002-06-26 Thread wixtc1117b32
Warning Unable to process data: multipart/mixed;boundary="=_NextPart_000_00B7_44E11C5B.D0815A74"