--- Marco Strack <[EMAIL PROTECTED]> wrote:
> Begin forwarded message:
>
> Date: Fri, 27 Feb 2004 11:59:22 -0600
> From: Steve Holland <[EMAIL PROTECTED]>
> To: Felix Khling <[EMAIL PROTECTED]>
> Subject: Re: [Dri-devel] savage-2-0-0 test notes
>
>
>
On Thu, 11 Mar 2004 20:13:44 +0100
Marco Strack <[EMAIL PROTECTED]> wrote:
[snip]
>
> Tuxracer is still fine. But blender didn't change. The screen is clean
> but all fonts are corrupted. It seems to me that the fonts in blender
> are also gl, but that's just an assumption.
The font corruption
Begin forwarded message:
Date: Fri, 27 Feb 2004 11:59:22 -0600
From: Steve Holland <[EMAIL PROTECTED]>
To: Felix Khling <[EMAIL PROTECTED]>
Subject: Re: [Dri-devel] savage-2-0-0 test notes
I tested it with a fresh copy from the trunk (effective tuesday),
--- Steve Holland <[EMAIL PROTECTED]> wrote:
> My apologies for being horribly slow to respond.
> The mode switching problem occurs with bpp=24 (bpp=32 didn't work at
> all
> for me). Hardware is SuperSavage/IXC SDR (ThinkPad T23).
> I do get the message:
>(==) SAVAGE(0): Using video BIOS to
My apologies for being horribly slow to respond.
The mode switching problem occurs with bpp=24 (bpp=32 didn't work at all
for me). Hardware is SuperSavage/IXC SDR (ThinkPad T23).
I do get the message:
(==) SAVAGE(0): Using video BIOS to set modes
But I get this regardless of whether I have the
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> Forwarding to dri-devel. Some of this (mode switching problem) looks
> like a 2D issue. Alex?
I'll have to double check, but I don't recall having any problems with
mode switching in tuxracer last time I played with it. Steve, what
chip are you runn
Forwarding to dri-devel. Some of this (mode switching problem) looks
like a 2D issue. Alex?
I don't know why drawpix to the backbuffer works for me but not for you.
I'll look into this some time. But it's no priority right now.
Hmm, I was just wondering if you have enough memory for 3D in 32bpp m
