On Mon, Nov 18, 2002 at 08:14:53PM -0800, Ian Romanick wrote:
|
| How does one go about determining the (data structure / API) version of
| libGL.so?
As I understand it, there isn't a formal version number. Apps that
follow the Linux ABI shouldn't need to be aware of the libGL version,
so there
On Fri, Nov 15, 2002 at 12:02:28PM -0700, Brian Paul wrote:
> This would involve implementing glXSwapInterval() as an ordinary
> function in libGL. It would simply stuff the interval value into
> the __GLXContextRec struct (assuming it's per-context). Then, it
> would be up to the DRI driver(s)
On Thu, Nov 07, 2002 at 04:32:03PM +, Keith Whitwell wrote:
>Michel Dänzer wrote:
>> On Don, 2002-11-07 at 16:56, Keith Whitwell wrote:
>>
>>>Michel Dänzer wrote:
>>>
These no longer get built by default. Any objections against the
attached patch?
>>>Actually if they're not built,
On Wed, Nov 06, 2002 at 03:43:02PM -0800, Ian Romanick wrote:
>> Is this hammered in stone?
>> When will we see the next XFree86 release (4.4.0), then.
>> Shouldn't OpenGL 1.4 better go in sooner then later?
>
>Would the Mesa 5.x merge be too large of a change for XFree86 4.3.1? There
Yes, it wo
I heard a while ago that some company was sponsoring the development
of a proper DRI driver for the ATI R200 -- can someone briefly update
me as to what the status of that driver is in the latest release and
in CVS? Is it a worthy replacement (in OpenGL performance and
stability) for the ATI binar
This is just a friendly reminder that the weeking dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.openprojects.net at 2100 UTC (or
4:00PM EST or 1:00PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
-
N¬±ùÞµéX¬²'²Þu¼¢W®{ay¶¬Ë(~Ǻ¸§*.¯²+^Â+aI"Ü'$
êÞ¶ µ¡QDÑ è}¤ák ^Iêïz°®ØÆzm§ÿðÃ(¶°µç(úÝçn!¶iC®'^½éfj)b b²ÐëׯzYb²Û,¢êÜyú+éÞ¶m¦Ïÿ+-²Ê.Ç¢¸ ë+-³ùb²Ø§~Ý®'^½é
I'm moving this thread to the dri-devel list, concerning multi-adapter
multi-head...
By adding '#define DRIVER_NUM_CARDS 2' to mach64_drv.c, we were able to
get the drm to initialize both devices (2 PCI Rage XL cards), but the
kernel messages show problems with locking and instability/reboots occu
Hi,
Thanks for your reply.
Ian Romanick wrote:
radeonUploadTexImages: ran into bound texture
I think this may be caused by a bug I found while doing some work on the
texmem branch. I believe that the exported maximum texture size is too big.
It may be possible that tuxracer is trying to do m
On Sun, Nov 17, 2002 at 02:53:37PM +0100, Manuel Bilderbeek wrote:
> When leaving the program, I can see lots of these messages from
> stdout/stderr:
> radeonUploadTexImages: ran into bound texture
I think this may be caused by a bug I found while doing some work on the
texmem branch. I believe
Brian Paul wrote:
Keith Whitwell wrote:
Brian Paul wrote:
CVSROOT:/cvsroot/dri
Module name:xc
Repository:xc/xc/lib/GL/mesa/src/drv/tdfx/
Changes by:brianp@usw-pr-cvs1.02/11/15 16:13:59
Log message:
Modified functions in __DriverAPIRec to remove unneeded Display *
param
-Original Message-
From: Ian Romanick [mailto:[EMAIL PROTECTED]]
Sent: 15 November 2002 20:40
To: DRI developer's list
Subject: Re: [Dri-devel] Adding GLX extensions?
[...]
> Hmmm...would adding it as a hard-coded extension make life easier for IHVs
> that want to provide binary-only dr
Ian Romanick wrote:
Hmmm...would adding it as a hard-coded extension make life easier for IHVs
that want to provide binary-only drivers but not necessarilly their own
libGL.so? I'm thinking ATI and PowerVR...
Oddly enough, ATI provides a libGL.so replacement in their package. I'm
not sure wh
13 matches
Mail list logo
