-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11.04.2014 08:31, Steve Langasek wrote: > On Thu, Apr 10, 2014 at 10:33:41PM +0300, Timo Aaltonen wrote: >>>> This would allow a more sane way to provide BDW support in >>>> 14.04.1 than backporting a big pile of commits and >>>> maintaining the franken-mesa ourselves.. > >>> Is 14.04.1 the right time frame to be targetting Broadwell >>> support, or should we be aiming for 14.04.2 instead? I.e., >>> would this fit better the normal point release hardware >>> enablement stack process? > >> I'm afraid 14.04.2 is too late for the first batch of devices to >> be shipped by our OEM partners "before EOY".. (being vague on >> purpose, the release schedules aren't public yet AIUI). That's >> also why the trusty kernel has a i915_bdw module backported from >> 3.14+fixes. Attempting the same for mesa is unknown territory >> though, kernel is easy in that regard. > > OK. I realize that trying to backport all the pieces onto mesa is > not necessarily less risky than taking the new upstream version; > but that just makes me worry that neither is appropriate for an > SRU. Have you considered the possibility of an early "pre-release" > version of the enablement stack, made available to OEMs that will > ship before EOY, and automatically updated to the official 14.04.2 > enablement stack once it's out?
Well, the deadlines are pretty aggressive.. that said, I got a patch from upstream before weekend that fixed the blocker bug running Unity on BDW*. Our driver test suite ran fine too, though some piglit tests obviously failed (due to missing features from the DRI driver) but didn't hang the machine or anything. So, I'm proposing to add this patch and the commit to enable BDW on i965_dri.so before the release, and we can then backport further fixes as SRU on a case-by-case basis? Might be that it's unnecessary to backport any massive features for 14.04.1 (HiZ, MSAA were the bulk of the preliminary backport work). I've requested to backport bugfixes to the stable queue for mesa 10.1.x, we'll see how that goes. * https://bugs.freedesktop.org/show_bug.cgi?id=75879 - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTS4JoAAoJEMtwMWWoiYTc4o8QAI+dvUVjDwxq+1CbXIxTSfsI mho5yrKcMyx55WBQ/YS76FhHCCBVHbULFZvnJLCLoR8gXWRUvGjMryiovDGNkld9 OQSPDh8LMAGmLRb5jH1/GhVTJ82oz6LoDjihJv+GRcu0D8/PPI7a0Old2hP4YZtB ymRF0pC4WIRUubtVghbwkebLqQ8iuySH/xm8IbrZKFKu6yk5EZ7ocFGa82nRHOS6 DXimh3i2XNXba17wEjNVJS+Q4+v85As7lwXYu4xNPAbRrzdnQX9eksNta4iIpnzk LlMPW/Kjbfy3xzRZIaTdF3Y6bGLin5Q47ccavV2hgUjqaG1yp7Z59oN8rDtVWNCD rSxt0p6nyN/vpRXaRXLBFMkPIIAnQIJF5IJVZ+knrftcc6sGGUOFsM/Axscqc8Zc OzdcTIMNvbf1vtX2sC1k8HgO1OauGPiDBXKADQFa3E6V0tEg/IMCKdAycF1DrSZi tDC4hzO4RNbmCf4eJ/9JfqvqXTqVS5b4w3HodMzkwEImzPiTpzIso5QQd/vHHnRG rOkrvVXjIlxdZwm/3xgOK4rWt/NkU5E4/tQufiU2chqUXlRibG72T7XcX7qS3XXc /37sBi+uAtjEeuQGdmUE0+pMn/CqlqKnqn9QuHXAOBfP8Ni4t0PUq9NEKTQCPHTz wvJr3lRIBkJ4NeCz6KDS =1cqp -----END PGP SIGNATURE----- -- Ubuntu-release mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
