Each driver currently exports only the fbconfigs that match the current color bits. This is wrong. The driver should export *all* the fbconfigs that it can support and let the loader figure out which ones should actually be exposed to the application.
If I change r200 to export all of it's fbconfigs, is the loader set up to figure out which configs to expose? Which loader are you referring to? I need to make this change in order to get EGL working.
This bug is no longer relevant. Now that the 3D driver is used in the server to determine what visuals / fbconfigs are available, there are a few more restrictions on what fbconfigs it should export.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.