On Thursday 23 January 2003 21:50, Pasi Kärkkäinen wrote:
I recommend using some library which has up-to-date header file and code to
automatically set up all supported extensions..
http://glew.sf.net is one of these. It supports most of ARB-, EXT-, ATI-
and NVIDIA-extensions under both Linux
So, I was thinking about some CPUs that are about to hit the market and
how they will interact with DRI. The main issue that I came across was
with x86-64. When x86-64 systems roll of the line, they'll
(eventually?) have 64-bit kernel support and (for legacy apps) 32-bit
user-mode support.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ian Romanick
Sent: Friday, January 24, 2003 12:29 PM
To: DRI developer's list
Subject: [Dri-devel] 64-bit kernel, 32-bit user. Possible? Painful?
So, I was thinking about some CPUs that are about
Title: RE: [Dri-devel] 64-bit kernel, 32-bit user. Possible? Painful?
My question is, what are the gottchas of having the DRM run
in a 64-bit
kernel and the rest of the driver run in either a 32-bit
application or
a 64-bit application? Will it even matter? If it will
matter, is
On Fri, Jan 24, 2003 at 06:18:46PM +0100, Gregor Riepl wrote:
On Thursday 23 January 2003 21:50, Pasi Kärkkäinen wrote:
I recommend using some library which has up-to-date header file and code to
automatically set up all supported extensions..
http://glew.sf.net is one of these. It
Rick Jones wrote:
I have acquired a Silicon Motion, Inc. Lynx3DM (SM720)
chip databook. I have a board with shared video
memory and 4MB on the chip.
You don't describe the circumstances under which you acquired
the databook, but you should be -real sure- that the company won't
take offense
On Fri, 24 Jan 2003 22:01:28 -0500
Mike Westall [EMAIL PROTECTED] wrote:
first before getting cvs access to commit?
YES!! You should be able to build it and test it in every torturous
way you can think of before even thinking of committing it.
Thats a little steep considering the 'alpha'
Hello.
I've been having some troubles with dri-cvs for some time when running
GL apps (especially the GL hacks that come with JWZs xscreensaver). In
particular, I've noticed problems when running endgame and menger on
the root and in windows and then running other windows over them or
moving
Would someone possibly do me the favour of either pointing me
to a [very] small program that tests basic drm
(Allocate DMA mem), (Read/Write DMA mem), (Free DMA mem)
functionality, or, if you are feeling particularly generous,writing one?
I'm not talking about excercising any specific video card
