On Tuesday, June 10, 2014 09:57:23 PM Matt Turner wrote: > Allows the compiler to cut dead code and simplify when we know the > driver will run on a single platform. Perhaps useful for distributions > wanting to ship new hardware support without the risk involved in > updating Mesa for existing hardware.
Huh, you sent out my old patch series that wasn't really going anywhere... :) My original thinking was to update the loaders to look for "ivybridge_dri.so", "broadwell_dri.so" (or maybe gen8_dri.so, gen7_dri.so, ...), which could simply be symbolic links to the traditional i965_dri.so. But, it would allow distributions to drop in a different driver for one platform. For example, distros could ship 10.3 for Broadwell while sticking with 10.1 or 10.2 for earlier platforms. Or, they could ship 10.2 for most things, but stay on 10.1 for <some platform> due to a regression. Whatever they wanted. The thought behind compiling custom versions was to use -march flags. For things like ChromeOS or Android, it makes sense to target a specific generation. Gentoo users could as well. Most distros probably wouldn't. I don't really have a strong opinion about it.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
