<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <body> <div dir="auto"> <div dir="auto">+1. I'd we think GLVND and X are ready for this, I think it's a good plan.</div><div dir="auto"><br></div> <div id="aqm-original" style="color: black;"> <div dir="auto">On March 22, 2021 17:34:09 Eric Anholt <eric@anholt.net> wrote:</div> <div><br></div> <blockquote type="cite" class="gmail_quote" style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;"> <div dir="auto">On Mon, Mar 22, 2021 at 3:27 PM Dylan Baker <dylan@pnwbakers.com> wrote:</div> <blockquote type="cite" class="gmail_quote" style="margin: 0 0 0 0.75ex; border-left: 1px solid #0099CC; padding-left: 0.75ex;"> <div dir="auto"><br></div> <div dir="auto">Hi list,</div> <div dir="auto"><br></div> <div dir="auto">We've talked about it a number of times, but I think it's time time to</div> <div dir="auto">discuss splitting the classic drivers off of the main development branch</div> <div dir="auto">again, although this time I have a concrete plan for how this would</div> <div dir="auto">work.</div> <div dir="auto"><br></div> <div dir="auto">First, why? Basically, all of the classic drivers are in maintanence</div> <div dir="auto">mode (even i965). Second, many of them rely on code that no one works</div> <div dir="auto">on, and very few people still understand. There is no CI for most of</div> <div dir="auto">them, and the Intel CI is not integrated with gitlab, so it's easy to</div> <div dir="auto">unintentionally break them, and this breakage usually isn't noticed</div> <div dir="auto">until just before or just after a release. 21.0 was held up (in small</div> <div dir="auto">part, also me just getting behind) because of such breakages.</div> <div dir="auto"><br></div> <div dir="auto">I konw there is some interest in getting i915g in good enough shape that</div> <div dir="auto">it could replace i915c, at least for the common case. I also am aware</div> <div dir="auto">that Dave, Ilia, and Eric (with some pointers from Ken) have been</div> <div dir="auto">working on a gallium driver to replace i965. Neither of those things are</div> <div dir="auto">ready yet, but I've taken them into account.</div> <div dir="auto"><br></div> <div dir="auto">Here's the plan:</div> <div dir="auto"><br></div> <div dir="auto">1) 21.1 release happens</div> <div dir="auto">2) we remove classic from master</div> <div dir="auto">3) 21.1 reaches EOL because of 21.2</div> <div dir="auto">4) we fork the 21.1 branch into a "classic-lts"¹ branch</div> <div dir="auto">5) we disable all vulkan and gallium drivers in said branch, at least at</div> <div dir="auto">the Meson level</div> <div dir="auto">6) We change the name and precidence of the glvnd loader file</div> <div dir="auto">7) apply any build fixups (turn of intel generators for versions >= 7.5,</div> <div dir="auto">for example</div> <div dir="auto">8) maintain that branch with build and critical bug fixes only</div> </blockquote> <div dir="auto"><br></div> <div dir="auto">I would like it if Intel could avoid garbage-collecting older-HW</div> <div dir="auto">shared code for at least a release due aforementioned WIPs, but I</div> <div dir="auto">think it's time to call the classic i965_dri.so and i915_dri.so done.</div></blockquote></div><div dir="auto"><br></div><div dir="auto">I'm happy to leave older hardware support in the tree for now. We need to keep the vec4 compiler for HSW Vulkan support for now and there's no harm in keeping old hardware support in ISL. I'm a little tempted to let HSW Vulkan bitrot in the LTS branch too but it does still pick up features here and there so I'm unsure if that's a good idea or not.</div><div dir="auto"><br></div><div dir="auto">--Jason</div><div dir="auto"><br></div><div dir="auto"><br></div><div id="aqm-original" style="color: black;" dir="auto"><blockquote type="cite" class="gmail_quote" style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;"><div dir="auto"></div> <div dir="auto">+1 from me assuming that we validate that one can actually get a</div> <div dir="auto">working X server with the mesa-legacy set installed.</div> <div dir="auto">_______________________________________________</div> <div dir="auto">mesa-dev mailing list</div> <div dir="auto">mesa-dev@lists.freedesktop.org</div> <div dir="auto">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</div> </blockquote> </div><div dir="auto"><br></div> </div></body> </html>