As I've said before, I'm going to be moving the Mesa project to
SourceForge.net in the near future.
Those of you on the Mesa developer's list should visit
www.sourceforge.net, register yourselves as users and join the
[EMAIL PROTECTED] mailing list. I will not be automatically
moving the member
emanuel stiebler wrote:
>
> Hi,
>
> Is it true, that the size of GLcontext is about 75 KByte ?
sizeof(GLcontext) ~= 72KB in Mesa 3.3. With all the other structs
and arrays that it points to it's probably several times that size.
> Is there any chance to get it smaller ?
Not much smaller.
W
Eero Pajarre wrote:
>
> While searching for a bug (which was elsewhere),
> I noticed that glPopAttrib doesn't seem to
> call the necessary driver functions for
> restoring the current "clear color"
>
> And there might be similar problems with the
> write masks...
>
> And I guess this is a typo:
emanuel stiebler wrote:
>
> Hi all,
>
> In osmesa, i can allocate my own framebuffer, which resides on my pci-card.
> But, what is the suggested/clean way to do the same with the depth-buffer ?
>
> Because I'm writing a driver for a card which has a rendering processor, it
> would be "nice" if
Hi all,
In osmesa, i can allocate my own framebuffer, which resides on my pci-card.
But, what is the suggested/clean way to do the same with the depth-buffer ?
Because I'm writing a driver for a card which has a rendering processor, it
would be "nice" if the depth-buffer would be on the card, an
