ever got this clear an answer when I asked in my most
official attempt to develop some kinda simple devel guide ..
Anyways, I am glad it's already starting to be useful to people (John Utz)
>I've given a couple presentations on the DRI, so maybe I can find one of
>those to post as w
Okay, sorry, I just had to laugh. Not your fault, I admit that. You are as innocent
as I used to be.
Here's the deal bro:
[RANT MODE ON]
Sometimes it seems that the DRI project is for a "special" group of people who are
(either,or,and,not,etc,etc):
1) special, either because they designed
1) is anyone still maintaining the Glide source/CVS ?
2) anyone noticed problems while compiling Glide3 for Voodoo5 with debug
on?
I get this error with the GL apps i tried (gears, Quake3, mine), except
glxinfo which seems ok:
gd.0: GLIDE DEBUG LIBRARY
gd.0: cpu: 0x6
_grVa
Can I compile the files in a driver directory alone, without having to do
the whole DRI or X11 tree ? Then grab the driver_dri.so file and throw
it in the modules directory and restart X11 for it to take effect ?
This assumes that the only changes are within the driver directory, and
not
In the below line of code, which file contains the definition of DRM(),
and is it a macro , and if so what exactly does it do to the function alloc()
?
radeon_cp.c:entry = DRM(alloc)( sizeof(drm_radeon_freelist_t),
Free, encrypted, secure Web-based email at www.hushmail.com
I don't want to beat it to death, but following the "Announcement" sparked
discussion I wanted to mention my take:
One of my problems (time being the biggest one of course :) with getting
involved with the code-part of the DRI project was the developer documentation.
I am greatful for having
At Fri, 08 Jun 2001 07:04:31 -0600, Brian Paul <[EMAIL PROTECTED]> wrote:
>
>[EMAIL PROTECTED] wrote:
>>
>> Just wondering if anyone else saw something like this unresolved symbol
>> in their X11 logs:
>>
>> (II) TDFX(0): Primary V_BIOS segment is: 0xc000
>> (II) TDFX(0): VESA BIOS detected
>>
Just wondering if anyone else saw something like this unresolved symbol
in their X11 logs:
(II) TDFX(0): Primary V_BIOS segment is: 0xc000
(II) TDFX(0): VESA BIOS detected
(II) TDFX(0): VESA VBE DDC supported
Symbol DRIMoveBuffersHelper from module /usr/X11R6/lib/modules/drivers/tdfx_drv.o
is u
Thanks for all the work Gareth, comments, help, emails, etc !! Wish you
the best of luck.
PS. hope they gave you a visa to make it to the states without sweat :)
Free, encrypted, secure Web-based email at www.hushmail.com
coz i can't get to sourceforge (goddamn their updates take LONG):
1) weird problem (and only one) in Q3A, when you go to setup your player
and you are selecting the color of your RAILGUN traces, then you only see
the selected color, and not the entire "spectrum" of possible colors
2) glTron
hi,
i'd like to know from those of you who have used the i810 and/or i815 chipsets
how well they work under DRI, and what kind of problems you might have come
up against etc etc
any info would be appreciated
thanks in advance
tony
ps. please email me at: adoniz_at_hushmail.com (replace _
I used the ATI Rage Mobility 4P i think it was (4mb chip) with the Utah-
glx drivers and it worked fantastically and faster than ATI's Winblows drivers
thanks to the efforts of Gareth Hughes.
I am not sure if it's supported under the DRI framework at all, but Utah-
glx was good enough for what
Ademar,
looking at your pasted info I see:
I'm using:
kernel 2.4.3
SiS 6326 chipset
and
OpenGL vendor string: Brian Paul
OpenGL renderer string: SiS 300/630/530 DR Mode
OpenGL version string: 1.2 Mesa 3.4
As far as I know the Sis 6326 is not the same as the Sis 630. I don't know
this with 1
I know this is a bit off topic (not totally because there's info on the
SiS 540/630 etc chipsets), but I wanted to share this info because I am
sure some of you might have been looking for it like i was ...
I found this site and it had quite a few PDF's that I was unable to get
my hands on fro
I think i saw this mentioned once, but i am not so certain, but are there
any thoughts or possibilities that the DRI project will get those cute (and
man!, so helpful) little performance/debug/whatever you want to call them
boxes on the top left of the screen ?(we could also use 1bit graf
Curious, but is that image up to date or have things changed any since
its inception?
and can someone tell me a little more about the GXlib module under the
Indirect Rendering module? (it's listed next to the Xlib module)
thx
Free, encrypted, secure Web-based email at www.hushmail.com
Thanks for the quick response Alan,
>SiS themselves dropped us the code quite some time ago and have not
>really updated the driver since the initial drop.
aha! that explains the fact that i haven't seen word about it on the lists..
>None of the active DRI developers have access to such c
I _did_ see (unless i was up waaay too late again) a SiS DRM driver in the
last DRI code I checked out, and also the corresponding SiS driver in the
X tree ...
I briefly looked inside and it said that it supports the SiS630/540 and
a couple other models...
Did i see things right? And why d
Adam your problem is shown in these lines from Q3:
Using XFree86-VidModeExtension Version 2.0
XF86DGA Mouse (Version 2.0) initialized
XFree86-VidModeExtension Activated at 640x480
Using 8/8/8 Color bits, 24 depth, 0 stencil display.
GL_RENDERER: Mesa GLX Indirect
Initializing OpenGL extensions
.
19 matches
Mail list logo