On Thu, May 03, 2001 at 08:53:32PM -0700, Eric Anholt wrote:
I've got diffs to get BSD DRM almost compiling for tdfx and mga up on my
site. Check bsd-2-0-0-branch diffs (and the drm_agpsupport.h file, I
didn't
feel like merging linux and bsd agp into a single file right now). They
are
On Thu, 3 May 2001, Joseph Carter wrote:
On Thu, May 03, 2001 at 09:47:23PM -0700, Jeffrey W. Baker wrote:
There also appears to be a conflict with the Radeon 64 and the KT133A (or
at least the Abit KT7A..)
I've got a KT133A and a Radeon All-in-Wonder, with no problems at all.
The
Why is this a problem? How many people out there are swapping back and
forth between a V3 and V5 on the same machine and need to change symlinks?
Adam
On Fri, 4 May 2001, Mike A. Harris wrote:
I'd like opinions on what would be the best way of determining at
runtime what glide library to
On Fri, 4 May 2001, Joseph Carter wrote:
On Fri, May 04, 2001 at 01:12:47PM +0100, Iain Thomas wrote:
As I said, it seems specific to the Radeon 64, the 32s have been reported
to work fine.
We all know that the various Radeons have differend core clock-speeds,
right?
We do now. =)
I'd like opinions on what would be the best way of determining at
runtime what glide library to use? The current problem is that
there are 2 Glide libraries for Glide3 - one for Voodoo 3, and
another for Voodoo 5. This is inconvenient to say the least.
Currently, we symlink libglide3.so.3.10.0
On Thu, May 03, 2001 at 08:15:19PM -0500, Andy Isaacson wrote:
On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
Would it be better if the DRI User Guide were divided into a number of
separate HTML pages, instead of one long document? I could do that
with the sgml2html
Ah, I see you're running into the same problem I did a while back.
(I'm the Debian glide maintainer.)
What we do is actually pretty close to that, I use debconf for the
interface though with a little work it could easily be split out.
Basicly at install time I use lspci to find the cards in the
Andy Isaacson [EMAIL PROTECTED] writes:
to create an account for just that purpose. If someone who already has
a SourceForge account could do so, I'd appreciate it...
Done. Request id 421523. Let's hope for a positive reply.
--
Marcelo
___
I have it disabled in my host.cf but it stops compilation.
Greetings,
Dieter
gcc -c -O -mcpu=k6 -fomit-frame-pointer -mpreferred-stack-boundary=2
-malign-functions=4 -fschedule-insns2 -fexpensive-optimizations -ansi -Wall
-Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes
When it comes 'bus lock up' and VIA chipset ... checkout
http://www.viahardware.com/ there you should find latest
via 'PCI latency patch' that also fixes ... (or supposed to fix)
such random locks up ...
btw. That patch is in the latest greatest kernels. including
2.4.3-acX (X 12) and later.
On Fri, May 04, 2001 at 08:19:44PM -0500, Andy Isaacson wrote:
On Sat, May 05, 2001 at 01:32:07AM +1000, Gareth Hughes wrote:
Adam K Kirchhoff wrote:
Speaking of which, I've been thinking about ordering Tribes2 and was
wondering if there are any issues that we should be aware of?
Go
On Fri, May 04, 2001 at 08:19:44PM -0500, Andy Isaacson wrote:
On Sat, May 05, 2001 at 01:32:07AM +1000, Gareth Hughes wrote:
Adam K Kirchhoff wrote:
Speaking of which, I've been thinking about ordering Tribes2 and was
wondering if there are any issues that we should be aware of?
Go
Andy Isaacson wrote:
On Sat, May 05, 2001 at 01:32:07AM +1000, Gareth Hughes wrote:
Adam K Kirchhoff wrote:
Speaking of which, I've been thinking about ordering Tribes2 and was
wondering if there are any issues that we should be aware of?
Go and buy this game. It rocks. Loki has
On Fri, 4 May 2001, Jon Niehof wrote:
For the DRI, the easiest solution would be to have the dri_tdfx.o
dynamically load the appropriate Glide. The X server knows what
hardware it is running on and passes that to the client (via the PCI
id). If you did this, you could also change the X tree
On Fri, 4 May 2001, Philip Willoughby wrote:
Any pre-existing code out there to solve this problem? I don't
have any 3dfx cards to test with at all, so any help getting a
solution happening would be great.
Thoughts/comments/suggestions, etc.?
What I would do, as a quick-and-dirty hack is make
My development machine tracks debian unstable pretty closely (apt-get
update apt-get -u upgrade every few days), and recently when I had a
chance to grab the latest DRI tree and built it, I had client programs
failing to start with
straum% gears
gears: error while loading shared libraries:
On Fri, May 04, 2001 at 09:22:59PM -0400, Zilvinas Valinskas wrote:
When it comes 'bus lock up' and VIA chipset ... checkout
http://www.viahardware.com/ there you should find latest
via 'PCI latency patch' that also fixes ... (or supposed to fix)
such random locks up ...
btw. That patch is
17 matches
Mail list logo
