Re: [Syllable-developer] Quick savage driver test requested

[Kristian V. D. V. <va...@li...>]

On Fri, 26 Jan 2007 18:34:44 +0100 (CET), Tim ter Laak <ti...@sc...> wrote:
> On Fri, 26 Jan 2007, Vandervliet, Kristian wrote:
>> Kristian Van Der Vliet wrote:
>> although there is a lot of
>> code that *only* applies to the (previously tested and working)
>> MobileSavage. Whatever the reason, it appears that the 2D engine
>> simply does not process any commands: acclerated rendering ops.
>> do not produce anything and calls to WaitIdle4() never return
>> normally. Disabling the COB makes no difference.
> 
> One thing, especially in the 2D accelleration, that bothers me for my
> ProSavageDDR too is that I'm not clear what tiling mode the Syllable
> driver uses. Actually, I don't even have a real idea what exactly tiling
> *is* in this context. Moreover, Savage4 seems to have a special case in
> SavageSetGBD_Twister...

The code is ported as if tiling is always switched off I.e. TILE_LINEAR is in
use. The only reason for the special case in SetGBD_Twister() is because
the BCI_ENABLE case is different, but otherwise identical.
 
> I'm not sure where exactly, but I remember from my (ongoing) effort to
> port the mode-switching code that there even are subtle differences
> between the xorg driver and the Linux kernel framebuffer driver. Have you
> already tried both on Linux?

I havn't explored the slim possibility that the card is broken, but I did try
making the code more DirectFB-like, but it made no difference. I suspect
it's a more fundemental problem with Initialise2DEngine() or SetGDB(),
but I see nothing.
 
> Other things I've been considering for the flickering problem on my own
> laptop, is side-effects from not running the card in AGP mode, or from
> differences in the Virtual x86 implementations (for the BIOS). Those are
> pretty wild suggestions though.

Yes, the Syllable driver doesn't touch the memory clock nor does it
enable AGP modes. Although Syllable itself doesn't enable AGP unless
you pass enable_agp=true to the kernel.
 
>> This has made me very nervous. Has anyone here tried a recent
>> version of Syllable (0.6.0 or newer) on a Savage video card
>> *other* the a Savage IX or MX? That includes the Savage3D,
>> Savage 4, Savage 2000 and ProSavage range. Did it work?
> 
> My ProSavageDDR, but obviously you already knew that ;)

I thought you were using a MobileSavage. Well that's good news at
least; it may only be the 4 that has a problem (Although the
framebuffer will also be incorrect for the Savage3D, too)

Hmm. Oh well, I'll see if I can come up with anything. Thanks Tim.

-- 
Vanders
http://www.syllable.org
http://www.liqwyd.com