<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unify the format conversion code" href="https://bugs.freedesktop.org/show_bug.cgi?id=84566#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unify the format conversion code" href="https://bugs.freedesktop.org/show_bug.cgi?id=84566">bug 84566</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to Iago Toral from <a href="show_bug.cgi?id=84566#c24">comment #24</a>) > Jason, what do you think we should do for GL_COLOR_INDEX + GL_BITMAP? > > Currently this is handled as a special case in the texstore.c ubyte path > (store_ubyte_texture), specifically, the special case handles extracting > indexed color data so that the incoming pixels can be represented as an RGBA > image, then do the conversion from RGBA to dst normally. > > We do not have a Mesa format for this combination. > > I think we have two options: > 1) I guess we could create a mesa_format, detect this case specifically in > the master function and handle it there. > 2) The other option would be to let clients deal with it. That would involve > letting them transform it to RGBA before they call the master function. > > What do you think? Option 2. Mesa internally hasn't supported color index in a long time, let's not add it back.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>