Ian Romanick wrote:
>
> On Wed, Mar 27, 2002 at 10:53:48PM +, Keith Whitwell wrote:
>
> > Actually I think the test is correct, and that I was thinking of 16 bit
> > textures plus a full set of mipmaps at the time. Thus the numbers should be
> > doubled in the 32 bit case, rather than halve
Alexander Stohr wrote:
>
> > > (This is based on the idea that a full set of mipmaps packs
> > perfectly to take
> > > up two times the size of the base texture). That's also
> > not true for all
> > > architectures...
> >
> > Ok, that explains a bit. However, in some circumstances we
> > may l
> > (This is based on the idea that a full set of mipmaps packs
> perfectly to take
> > up two times the size of the base texture). That's also
> not true for all
> > architectures...
>
> Ok, that explains a bit. However, in some circumstances we
> may loose a
> level. The mipmaps don't dou
On Wed, Mar 27, 2002 at 10:53:48PM +, Keith Whitwell wrote:
> Actually I think the test is correct, and that I was thinking of 16 bit
> textures plus a full set of mipmaps at the time. Thus the numbers should be
> doubled in the 32 bit case, rather than halved for 16 as Leif was suggesting.
Ian Romanick wrote:
>
> On Wed, Mar 27, 2002 at 03:17:56PM -0500, Leif Delgass wrote:
>
> > In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
> > 4 bytes/texel is assumed when calculating for the max texture size. If we
> > always convert to 2 bytes/texel for a 16bpp screen
Oops, i should better care for sending
things to the mailing list address.
-Original Message-
From: Alexander Stohr
Sent: Wednesday, March 27, 2002 22:14
To: 'Leif Delgass'
Subject: RE: [Dri-devel] Max texture size
No, i dont see problems with that.
When the resoultion c
On Wed, 27 Mar 2002, Daryll Strauss wrote:
> On Wed, Mar 27, 2002 at 04:00:55PM -0500, Leif Delgass wrote:
> > On Wed, 27 Mar 2002, Alexander Stohr wrote:
> > > > So we'd use
> > > > mach64Screen->cpp for the calculation instead of a fixed 4
> > > > bytes/texel?
> > > > Then the comparison would
On Wed, Mar 27, 2002 at 03:17:56PM -0500, Leif Delgass wrote:
> In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
> 4 bytes/texel is assumed when calculating for the max texture size. If we
> always convert to 2 bytes/texel for a 16bpp screen when choosing texture
> formats
Leif Delgass wrote:
>
> In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
> 4 bytes/texel is assumed when calculating for the max texture size. If we
> always convert to 2 bytes/texel for a 16bpp screen when choosing texture
> formats, shouldn't that be factored into the cal
In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
4 bytes/texel is assumed when calculating for the max texture size. If we
always convert to 2 bytes/texel for a 16bpp screen when choosing texture
formats, shouldn't that be factored into the calculation? So we'd use
mach64S
10 matches
Mail list logo
