> It seems to me that the accelleration driver should decide that the Z > Buffer must be setup as soon as the first 3D call is made. But in Jons > approach, memory management seems to be done in the Chipset driver. In my > head, a "what belongs where" problem is playing around. This depends on the card. It might be, that it is possible to set up the Z buffer at a late time. However it might as well be, that it must be done at mode setup time (or the mode must be re-setup). An example would be an "inlined" Z buffer, that is interleaved with the pixel data. So basically I'd say it depends on the card. And as long as the LibGGI driverlib module knows how to access it, it should be irrelevant where it is implemented. CU, Andy -- = Andreas Beck | Email : <[EMAIL PROTECTED]> =
- Re: Doesn't need vertical retrace! Jos Hulzink
- Re: Doesn't need vertical retrace! Jon M. Taylor
- Re: Doesn't need vertical retrace! Andreas Beck
- Re: Doesn't need vertical retrace! Rub�n
- Re: Doesn't need vertical retrace! Andreas Beck
- Re: Doesn't need vertical retrace! Rub�n
- Re: Doesn't need vertical retrace! becka
- Re: Doesn't need vertical retrace! Marcus Sundberg
- 3D ioctls and other new stuff in KGI Jon M. Taylor
- Re: 3D ioctls and other new stuff in KGI Jos Hulzink
- Re: 3D ioctls and other new stuff in KGI Andreas Beck
- Re: 3D ioctls and other new stuff in KGI Jon M. Taylor
- KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Jos Hulzink
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Rub�n
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Andreas Beck
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Jon M. Taylor
- Re: KGI_COMMANDS James Simmons
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Jos Hulzink
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! becka
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Jon M. Taylor
- Re: KGI_COMMANDS, was: Re: Doesn't need vertical retrace! Andreas Beck
