On Mon, 10 Oct 2011 21:05:33 -0600, Brian Paul <brian.e.p...@gmail.com> wrote: > From: Brian Paul <bri...@vmware.com> > > Instead of the renderbuffer pointer. In the future, attaching a texture > may not mean the renderbuffer pointer gets set too. > Plus, remove some commented-out assertions.
I'm curious where you're going with not having a Renderbuffer for textures. I've wished that Mesa core handled making a Renderbuffer for textures, since there was this ugly driver code for cooking up a Renderbuffer even though everyone's should be basically the same. Maybe having the Renderbuffer go away will help, I'm not sure. In the rbmapping in swrast, I'm constantly wanting to know the format of fb->Attachments[WHATEVER] and get a mapping of it. I think that's the most important to have easy access to, whether it's from the Renderbuffer or helper functions on the attachment point (but it's sure easier to be able to pass a gl_renderbuffer around than fb+attachment).
pgpFhTkSFsHF3.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
