On Thu, Jul 08, 2004 at 08:07:50AM -0700, Ian Romanick wrote:
[EMAIL PROTECTED] wrote:
I am developing a new DRI driver based on XFree86 4.3.0,Mesa 4.0.4,and
redhat9.0.
You might be better off basing your driver on a more recent Mesa tree.
Right now, the open-source drivers live in
I am developing a new DRI driver based on XFree86 4.3.0,Mesa 4.0.4,and redhat9.0.
Because my hardware can do TCL,I hook my tcl render stage into mesa's pipe,and
make it as the first stage,just like r200 driver.
In my run_tcl_render, I don't use mesa's template file t_dd_dmatmp2.h to
generate
On Tue, Jun 29, 2004 at 08:35:53PM +0800, [EMAIL PROTECTED] wrote:
If I don't use gcc -O2 flag to compile dri driver,quake3 can run
smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until the
menu
comes up.
Umm,
If I don't use gcc -O2 flag to compile dri driver,quake3 can run smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until the menu
comes up.
If some variables should be protected by volatile,such as mmio address,
DMA buffer?
On Tue, Jun 29, 2004 at 09:56:56PM +0800, Dave Airlie wrote:
If I don't use gcc -O2 flag to compile dri driver,quake3 can run
smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until
the menu
comes up.
also
