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 : 1
Allocated 8 megs of GART memory
MemoryBenchmark: 521 mb/s
MemoryBenchmark:
Warning
Unable to process data:
multipart/mixed;boundary==_NextPart_000_00B7_44E11C5B.D0815A74
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 : 1
Allocated 8 megs of
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 :
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
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:
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
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, what was the problem?
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 code on
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 is
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 easy
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 event
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
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 merge in
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.
When [and if] the
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 branch
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 sticky
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 try as root. If
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
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 up for the
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 Mesa 4.0.3
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 trunk into a
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-branch in
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 definetly
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 |
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-externs
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 conflicts by
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 forgoten when
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'll
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
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 512
- 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]
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_context.h
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
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 and
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 it
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
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 have no
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_IOC(),
39 matches
Mail list logo
