Re: Fw: Re: [Dri-devel] savage-2-0-0 test notes

[Alex D. <ag...@ya...>]

--- Marco Strack <ms...@gm...> wrote:
>  >>>> Begin forwarded message:
>  >>>>
>  >>>> Date: Fri, 27 Feb 2004 11:59:22 -0600
>  >>>> From: Steve Holland <sd...@co...>
>  >>>> To: Felix Khling <fx...@gm...>
>  >>>> Subject: Re: [Dri-devel] savage-2-0-0 test notes
>  >>>>
>  >>>>
>  >>>> I tested it with a fresh copy from the trunk (effective
> tuesday),
>  >>
>  >>
>  >> and
>  >>
>  >>>> have the same problems.
>  >>>> Here are some PNG's of the results from drawpix:
>  >>>> 16 bit display, drawing to back buffer:
>  >>>> http://69.5.151.193/~sdh4/drawpix16bit.png
>  >>>> drawing to front buffer:
>  >>>> http://69.5.151.193/~sdh4/drawpix16bitfrontbuffer.png
>  >>>> 24 bit display drawing to back buffer: 
> http://69.5.151.193/~sdh4/drawpix24bit.png
>  >>>> (24 bit display drawing to front buffer was similar to
> 16->front
>  >>>> buffer)
>  >>>>
>  >>>> I also noticed problems when switching video modes on a 24 bit
>  >>>> display. For example, running tuxracer would get the display 
> parameters
>  >>
>  >>
>  >> wrong,
>  >>
>  >>>> leading to an incomprehensible display (even after quitting).
>  >>>>     Thanks,     Steve
>  >>>>
> 
> 
> The code i'm running is also about 2-3 days old. I've got the same 
> Hardware (T23 - supersavage IX/SDR).
> 
> What he means with corruption occurs when changing the display mode 
> "on-the-fly". Then the screen is corrupted. Switching back to the old
> 
> resolution normalizes the screen again.
> 
> This won't happen when starting initialy with the new setting. So 
> setting  XF86Config to a new res and restart X everything is fine.
> 
> 
> 
>   Acceleration stuff :
> 
> -only works in 16 bpp (2d/3d)
> -in 24bpp there is no 2d nor any 3d accelleration.
> -2D accell worked with tims driver on 24bpp.

regarding the 24 bpp stuff.  I'm not sure why that isn't working.  once
problem might be that the layout of the GBD might be wrong in the
driver.  I assumed it was like prosavage, but it might be like savage4
or m7.  I just made an educated guess when I added the code.  still if
it works at 16 bit, it should work at 24 bit.  if you want you can try
changing the BD setup for supersavage in savage_accel.c and
savage_dri.c.  I can explain in more detail or provide a patch.  it may
also be that you just don't have enough mem in 24 bpp.

Alex


> 
> 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.
> 
> 
> Besides that you did a _GREAT_ work, and the driver speeded up in the
> 
> last 2-3 Months as gar as i can see.
> With savage-2-0-0 i had about 270 fps in the beginning of working 
> dri-support for my chip. Than it got from 325 to 378.
> And with the last code in the savage branch it reached 408. That
> stayed 
> with the HEAD Branch since then.
> 
> 
> 
> 
>    regards marco
> 
> 


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com