[reposting... attachments caused message to be killed]
On Wed, Dec 10, 2003 at 12:53:53PM +0200, Ville Syrjälä wrote:
If you remove/comment out the following line
$(MAKE_CMD) $(MFLAGS) $(WORLDOPTS) World
in the top Makefile make World shouldn't actually build anything.
After that
On Wed, 10 Dec 2003 09:26:59 +
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
I briefly tried the DRI trunk after the newmesa merge last night. In
flightgear with TCL enabled the old lighting problem seems to be back.
Everything is too dark, but banking to one
Steve,
There are lots of things to be done with the savage driver. At the
moment I can hardly make the time to port it to current Mesa and the
recent change to Mesa 5.0.2 won't exactly speed this up. Here is a list
of the most important issues on the TODO list (in arbitrary order) for
the savage
On Wed, Dec 10, 2003 at 06:32:18AM -0600, Ryan Underwood wrote:
On Wed, Dec 10, 2003 at 12:53:53PM +0200, Ville Syrjälä wrote:
If you remove/comment out the following line
$(MAKE_CMD) $(MFLAGS) $(WORLDOPTS) World
in the top Makefile make World shouldn't actually build anything.
On Thu, Dec 11, 2003 at 02:02:36PM +0200, Ville Syrjälä wrote:
I don't run XFree86 except when trying to hunt DRI related bugs. It's
been well over a year since I really used XFree86 and I honestly don't
remember if DPMS ever worked with the second head. I don't have a second
monitor to
Am Donnerstag, 11. Dezember 2003 07:08 schrieb Dave Airlie:
I'm trying to valgrind my application and in the process DRI :-),
However I can't get over the Mesa MMX checks, is there any env variable I
can set so Mesa doesn't do all the stuff that requires SIGFPE and I can
force it to use a
Dave Airlie wrote:
I'm trying to valgrind my application and in the process DRI :-),
However I can't get over the Mesa MMX checks, is there any env variable I
can set so Mesa doesn't do all the stuff that requires SIGFPE and I can
force it to use a certain type of instruction set?
Try setting the
Eric Anholt wrote:
On Tue, 2003-12-09 at 10:29, Brian Paul wrote:
Alan Hourihane wrote:
On Tue, Dec 09, 2003 at 09:58:44AM -0800, Jon Smirl wrote:
--- Alan Hourihane [EMAIL PROTECTED] wrote:
[...]
I think SourceForge has fixed the CVS problems of times gone by.
If SF's CVS causes problems, I'm OK
in the past Valgrind was likely to choke on anything
but pure gcc generated assembler and binary code.
this means an sort of hand coded assembler,
non-default calling convention and alikes
could bring that checker to a halt.
to my best knowledge you could not even guide
that tool to ignore
Am Donnerstag, 11. Dezember 2003 07:08 schrieb Dave Airlie:
I'm trying to valgrind my application and in the process DRI :-),
However I can't get over the Mesa MMX checks, is there any env variable I
can set so Mesa doesn't do all the stuff that requires SIGFPE and I can
force it to use a
Hi all,
There is now a new set of trunk snapshots available at
http://dri.freedesktop.org/~fxkuehl/snapshots that was built after the
newmesa merge. Unfortunately I didn't manage to set up the a cron-job
for the build yet.
Regards,
Felix
On Thu, 11 Dec 2003 08:59:54 -0800
Felix Kuehling
On Thu, 11 Dec 2003, Felix Kühling wrote:
There's probably more. So to answer your question, VBLANK IRQ support is
not going to happen in the very near future.
Do you have any information on how to enable the IRQ on the Savage cards?
I've been looking around and have seen absolutely no
On Thu, 11 Dec 2003, Felix Kühling wrote:
If you are talking about low level hardware mechanisms to activate the
IRQ, I have no idea. Unfortunately I have no hardware specifications
available. BTW, where would you look for such information? ;-)
Yes, I was talking about low level mechanisms.
13 matches
Mail list logo
