Felix Kühling wrote:
> Hi,
>
> I have some questions about OS specific ways to find out the name of a
> running programme outside function main.
extern chat *__progname;
works on OpenBSD, NetBSD and Linux.
-d
---
This SF.Net email is spon
Chris Cheney wrote:
> I am considering buying a R350 based video card. However, currently
> even the official binary only ATI drivers do not support it. I saw
> that earlier this year someone asked if ATI had released any
> documentation on the R300/R350 chipsets to the DRI developers for 3D
>
Philip Brown wrote:
On Mon, Jan 27, 2003 at 11:18:43PM +0100, Felix Kühling wrote:
If anyone has serious objections to XML, please let us know (mail to
dri-devel will suffice ;-).
I object. Using xml inevitably leads to files that are completely
human-unreadable, except perhaps to the origina
Geoffrey Antos wrote:
I believe that it is safe to go ahead and implement S3TC texture
decompression code in DRI.
I don't understand why it is not possible for DRI to support S3TC on
hardware that implements it. In this case the DRI wouldn't be
*implementing* S3TC, just handing over pre-compre
Michel Dänzer wrote:
On Mon, 2002-10-28 at 01:55, Damien Miller wrote:
The fact that it grows doesn't necessarily mean a memleak in the server
- only if the growth is unbounded.
Which would seem to be the case if it starts growing from 220 M
immediately when it's only 90 M on sta
Michel Dänzer wrote:
On Son, 2002-10-27 at 23:58, Damien Miller wrote:
Memory can only ever increase for processes which do memory allocation
using brk() - there is no way to return such memory to the OS.
Interesting, but if that was all there is to it, then the apparent
memory usage should
Felix Kühling wrote:
Hi,
I had my Xserver running for about 24 hours straight and noticed that it
was using about 220M virtual memory. Even after closing all clients and
logging out the memory usage didn't drop significantly. After I killed
and restarted gdm it uses "only" about 90M. Does this in
On Mon, 2002-07-08 at 20:58, Michel Dänzer wrote:
> > 2) when is the GATOS code planned for merging?
>
> Never with the DRI repository directly. Apparently their Mach64 stuff is
> getting merged into XFree86 for 4.3.0, don't know about the rest. It
> should then get into the DRI repository when
Hi,
I can reliably lock up XFree 4.2.0 (on Redhat 7.3):
1. Reboot to Win2k
2. Play a DirectX or OpenGL game
3. Reboot to Linux
4. Try to start quake3
Usually I'll get a couple of frames drawn and the X server will lock. I
can ssh in, but can't shutdown cleanly.
Subsitiuting step (3) with a p
On Thu, 2 May 2002, Smitty wrote:
> btw the list is now up on the (card) status page of dri.sourceforge.net.
It would be really good if the status included what features are supported
by the hardware. This may make it easier for interested parties to jump in
and pick up pieces that they want t
On Tue, 9 Apr 2002, Raystonn wrote:
> If you want to get back to the topic of software rendering, I would be more
> than happy to oblige.
Better yet, if you are serious - how about furthering your argument with
patches to optimise and improve Mesa's software paths?
___
memory. Try dropping it and seeing of the screensavers
work.
Would the AGP texturing patch for the Matrox cards that was floating
around the list a few weeks ago help here?
-d
--
| By convention there is color, \\ Damien Miller <[EMAIL PROTECTED]>
| By convention sweetness, By conv
bits.
Does this mean that Radeon 7500 card are supported by DRI CVS? How about
8500 cards?
-d
--
| By convention there is color, \\ Damien Miller <[EMAIL PROTECTED]>
| By convention sweetness, By convention bitterness, \\ www.mindrot.o
still run the quake2 binary release which I first
used on Redhat 5.something on Redhat 7.1. Quake3 runs better on my Redhat
Frankenstein Roswell/Rawhide workstation than it did on Redhat 6.2.
-d
--
| Damien Miller <[EMAIL PROTECTED]> \ ``E-mail attachments are the poor man's
|
14 matches
Mail list logo
