I believe this is also missing in the MGA driver. The symptoms can be
seen for instance in the gflux demo. Part of the waving square is not
drawn.
Regards,
Felix
On Sat, 20 Dec 2003 04:44:31 -0800
Felix Kuehling [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/dri
Module name: xc
Repository:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two problems. One with
tnl/t_vb_render.c, the other one with tnl_dd/t_dd_tritmp.h. Both started
since I use different hardware primitives for quads and
triangles/polygons.
TAG(quad) in t_dd_tritmp.h calls RASTERIZE( GL_TRIANGLES
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two problems. One with
tnl/t_vb_render.c, the other one with tnl_dd/t_dd_tritmp.h. Both started
since I use different hardware primitives for
At 02:53 PM 18/12/2003, Felix Kühling wrote:
Take a look at
xc/programs/Xserver/hw/xfree86/drivers/savage/savage_bci.h. There are
conditionals
#if SAVAGE4
...
#endif
Try defining
#define SAVAGE4 1
I did that and things got better now. The 2D is still currupted if i don't
use the option
hi
I want to ask a questions, specially to Felix whose video card is the same
as mine.
When I start X my console text seems to stretch vertically and doesnt fit
in the screen, also, when I run X in 1024x768 when I switch to 800x600
some part of the screen at the botton is cut, I try to set
as I recall the savage hardware needs a tiled framebuffer for the 3d
engine, but 2d engine can use linear or tile. Most drivers use linear,
so that's probably what the savage driver did originally, now that it
has 3D support you need to get 2d working in tile mode for both to
work. there may just
On Sat, 20 Dec 2003 09:08:50 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
as I recall the savage hardware needs a tiled framebuffer for the 3d
engine, but 2d engine can use linear or tile. Most drivers use linear,
so that's probably what the savage driver did originally, now that it
has
Pablo,
I see exactly the same problem that you describe. I just didn't look
into it because it doesn't really bother me. I use 1024x768 in X and
also on the text console via vesafb because screen stretching looks
really ugly.
We should probably get in touch with Tim Roberts who maintains the
On Sat, Dec 20, 2003 at 01:47:24PM +0100, Felix Kühling wrote:
I believe this is also missing in the MGA driver. The symptoms can be
seen for instance in the gflux demo. Part of the waving square is not
drawn.
I fixed the mga swapbuffers code a few weeks ago.
On Sat, 20 Dec 2003 04:44:31
At 02:58 PM 20/12/2003, Felix Kühling wrote:
We had a similar problem with the 2D driver on the savage-1_0_0-branch.
Accelerated stuff worked just fine for me but direct frame buffer access
was broken. It turned out to be quite simple to fix. However, this fix
didn't work for Maximo, so I suspect
10 matches
Mail list logo
