On Thu, 8 Jan 2004 15:40:55 -0800 (PST) Alex Deucher <[EMAIL PROTECTED]> wrote:
> well, I managed to fix the 2D corruption in tile mode on savage4. the > problem is that the bits of the GBD (MM816C) have different meaning on > savage4 vs. twister/prosavage. The fix is to use the > SavageEnableMode_M7() function for savage4 rather than > SavageEnableMode_Twister(). This also negates the need to define > SAVAGE4 in savage_bci.h since SavageEnableMode_M7() already uses 8 for > BCI_ENABLE. > alternatively you can edit the SavageEnableMode_Twister() to use the > proper values, but the results are the same (and you don't break > twister/prosavage). I don't understand. How would using SavageEnableMode_M7 for Savage4 break ProSavage? > > with tiling mode fixed, 3D behaves similarly to linear mode. the 3D > app runs, but is scrambled somewhat. I'm not sure where the fix for > that lies, probably on the 3D side. Are you sure that tiled mode is enabled correctly? I think Rafael reported earlier that 3D (glxgears) worked ok for him with tiled mode enabled, even though 2D was garbled. > > Also, with regard to VT switches, I haven't seen any lockups. Then it's probably something specific to ProSavage. :-( > > Alex > ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything [EMAIL PROTECTED] \___/ \___/ U at the same time. ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
