On Fri, 2004-02-20 at 15:17, Chris Ison wrote:
I brought an AGP Radeon 9200SE yesterday, thinking I would get a HUGE
performance increase over my older PCI Radeon 9000. And for windows
sure enough, the overkill demo in quakeforge jumped from 33fps to
122fps within Windows.
When I tried it
You know how to verify that...
I've actually forgotten how, I think its an enviroment setting, but none of
the settings I saw when I grep's getenv triggered my memory.
I'm sure you've tried page flipping and ruled out things like usleeps in
the client side drivers?
usleeps in dri? there
Alex Deucher wrote:
--- Chris Ison [EMAIL PROTECTED] wrote:
I brought an AGP Radeon 9200SE yesterday, thinking I would get a HUGE
performance increase over my older PCI Radeon 9000. And for windows
sure enough, the overkill demo in quakeforge jumped from 33fps to
122fps within Windows.
When I
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/dri
Module name: xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
Log message:
- fix console corruption. rather than
Am Freitag, 20. Februar 2004 13:49 schrieb Steve Dawson:
Alex Deucher wrote:
--- Chris Ison [EMAIL PROTECTED] wrote:
I brought an AGP Radeon 9200SE yesterday, thinking I would get a HUGE
performance increase over my older PCI Radeon 9000. And for windows
sure enough, the overkill demo in
Am Freitag, 20. Februar 2004 08:39 schrieb Erdi Chen:
This is a patch to call the context handles destructors and free the
context bitmap entries when a process does not destroy its contexts
before it exits. It saves context handles in a linked list in the
drm_device struct. I decided to use
On Thu, 19 Feb 2004 18:26:50 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
Hello S3 Savage users,
[snip]
Felix,
I'd like to give you a hand on the 3D driver while I still have some
free time, but I have to admit, I'm somewhat
On Thu, 19 Feb 2004 18:58:25 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
[snip]
I really interested on helping, specially on savage4 driver because is the
only one i have access, unfortunately i don't have much experience on
hardware programing but i'm learning a lot checking the savage
Felix,
How about dropping your current DRI savage driver into the Mesa trunk (6.1)
and whipping the driver into shape with the current DRI trunk.
I think that will serve you best, in that Mesa 5.x is obviously being
left behind now, and if you hit problems they may be bugs in 5.x your
hitting.
Dieter Nützel wrote:
Am Freitag, 20. Februar 2004 08:39 schrieb Erdi Chen:
This is a patch to call the context handles destructors and free the
context bitmap entries when a process does not destroy its contexts
before it exits. It saves context handles in a linked list in the
drm_device struct.
Felix Kühling wrote:
The last one is the easier one I think. In savagetex.c in
savageUpdateTex0State_s4 and savageUpdateTex1State_s4 there is a pretty
fancy computation of the 9bit LOD bias (probably some fixed point
format) from a floating point value. The lodbias mesa demo shows no
visible
--- Dieter Nützel [EMAIL PROTECTED] wrote:
Am Freitag, 20. Februar 2004 13:49 schrieb Steve Dawson:
Alex Deucher wrote:
--- Chris Ison [EMAIL PROTECTED] wrote:
I brought an AGP Radeon 9200SE yesterday, thinking I would get a
HUGE
performance increase over my older PCI Radeon 9000. And
On Fri, 20 Feb 2004 08:04:43 -0800
Ian Romanick [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
The last one is the easier one I think. In savagetex.c in
savageUpdateTex0State_s4 and savageUpdateTex1State_s4 there is a pretty
fancy computation of the 9bit LOD bias (probably some fixed
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module name:xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
Log
On Fri, 20 Feb 2004 14:55:55 +
Alan Hourihane [EMAIL PROTECTED] wrote:
Felix,
How about dropping your current DRI savage driver into the Mesa trunk (6.1)
and whipping the driver into shape with the current DRI trunk.
Are you suggesting to continue development on DRI trunk or make a new
On Fri, Feb 20, 2004 at 05:30:57PM +0100, Felix Kühling wrote:
On Fri, 20 Feb 2004 14:55:55 +
Alan Hourihane [EMAIL PROTECTED] wrote:
Felix,
How about dropping your current DRI savage driver into the Mesa trunk (6.1)
and whipping the driver into shape with the current DRI trunk.
Ian Romanick wrote:
1. Enable GLX_SGI_make_current_read support in all drivers. The MGA
driver already supports this extension. I did a patch once, which I'll
have to find, that enabled it for r200, but the patch only worked with
pageflipping disabled. People can start working on this now,
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module name:xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
Log
On Fri, 20 Feb 2004 08:28:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/dri
Module name: xc
Repository:
On Fri, 20 Feb 2004 09:25:50 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/dri
Module name: xc
Repository:
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 20 Feb 2004 08:28:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module
Erdi Chen wrote:
This is a patch to call the context handles destructors and free the
context bitmap entries when a process does not destroy its contexts
before it exits. It saves context handles in a linked list in the
drm_device struct. I decided to use per device list instead of a per
file
Ian Romanick wrote:
Ian Romanick wrote:
1. Enable GLX_SGI_make_current_read support in all drivers. The MGA
driver already supports this extension. I did a patch once, which
I'll have to find, that enabled it for r200, but the patch only worked
with pageflipping disabled. People can start
Since I have access to both a 9200SE and an 8500 (but not a 9000 or 9200,
unfortunately), I decided to run a quick benchmark with the cards using
ut2003. With the Inferno Flyby, I got the following results with the
9200:
5.294707 / 14.600776 / 133.766464 fps rand[1951333785]
Score =
And, for comparison, the same benchmark, on the same system, with the
FireGL drivers from ATI.
9200:
18.798862 / 39.684578 / 184.560455 fps rand[1951333785]
Score = 39.461594
8500:
20.887423 / 44.828197 / 195.236023 fps rand[1951333785]
Score = 44.228085
Adam
On Fri, 20 Feb
Alan Hourihane wrote:
On Fri, Feb 20, 2004 at 05:30:57PM +0100, Felix Kühling wrote:
On Fri, 20 Feb 2004 14:55:55 +
Alan Hourihane [EMAIL PROTECTED] wrote:
Felix,
How about dropping your current DRI savage driver into the Mesa trunk (6.1)
and whipping the driver into shape with the current
Erdi Chen wrote:
This is a patch to call the context handles destructors and free the
context bitmap entries when a process does not destroy its contexts
before it exits. It saves context handles in a linked list in the
drm_device struct. I decided to use per device list instead of a per
file
Dave Airlie wrote:
mach64. I'd do the same with savage.
Either way, seeing as the driver would be in the Mesa trunk, DRI branches
don't seem to make much sense anymore to me, unless it's for work on GLX
like the work Ian's doing.
The whole point of DRI branches before was to isolate new driver
On Fri, Feb 20, 2004 at 10:45:54PM +, Dave Airlie wrote:
mach64. I'd do the same with savage.
Either way, seeing as the driver would be in the Mesa trunk, DRI branches
don't seem to make much sense anymore to me, unless it's for work on GLX
like the work Ian's doing.
The whole
Hi,
DPMS never worked on my notebook with ProSavageDDR. The problem is that
the register that controls HSync and VSync signals of the CRT doesn't
have any effect on the LCD display. The attached patch disables the LCD
display via the bios if the DPMS mode is anything but ON. Alex, if you
think
--- Dave Airlie [EMAIL PROTECTED] wrote:
mach64. I'd do the same with savage.
Either way, seeing as the driver would be in the Mesa trunk, DRI
branches
don't seem to make much sense anymore to me, unless it's for work
on GLX
like the work Ian's doing.
The whole point of DRI
ok, let me get this in perspective
R9200R8500
DRI14.62103716.860273
fglrx39.46159444.228085
I have been trying to hunt down the slowdown in DRI, I even if (0)'s all
occurances of sched_yield () which is slower in 2.6 than 2.4 due to 2.6
doing it properly.
--- Tim Roberts [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Felix Kühling [EMAIL PROTECTED] wrote:
3. Separate commands and data
Right now commands and data are submitted to the chip as one data
stream, either via the BCI or via DMA buffers. For easier security
checking
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
DPMS never worked on my notebook with ProSavageDDR. The problem is
that
the register that controls HSync and VSync signals of the CRT doesn't
have any effect on the LCD display. The attached patch disables the
LCD
display via the bios if the
On Thu, 2004-02-19 at 15:46, Felix Kühling wrote:
I don't see a reason to mess with Mesa on the savage-2-0-0-branch now.
ok,
This is not my code, this is Brian Paul code.
So please apply, I remember, at the time of release Mesa-5.0.2, Brian
release one version of Mesa-5.0.2 to test, after this,
Bugs item #901568, was opened at 2004-02-20 22:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=100387aid=901568group_id=387
Category: None
Group: Documentation Error
Status: Open
36 matches
Mail list logo
