Re: [Mesa-dev] Mesa 17.2.0 release plan
On 24 July 2017 at 08:52, Marc Di Luzio wrote: > Hi Emil, > > This shouldn't block the RC, but it's something to make sure we have > fixed before the 17.2 final release. > > We're currently tracking a black screen bug hitting most of our game > backlog - https://bugs.freedesktop.org/show_bug.cgi?id=101867. > > Just pinging in to make sure we're aware, hopefully we'll have a fix > cc'd within the week. > Thanks for the notice Marc. This is the second serious bug that I've considered a blocker. The prime one being [1] which affects Steam on radeonsi. While the offending patch addresses earlier major breakage. Although it's unclear if restricted to radeonsi (and swr, respectively) or not. That said, I'm inclined that we can go with RC1 and address the issues in the following days/week. Thanks Emil [1] https://bugs.freedesktop.org/show_bug.cgi?id=101876 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
Hi Emil, This shouldn't block the RC, but it's something to make sure we have fixed before the 17.2 final release. We're currently tracking a black screen bug hitting most of our game backlog - https://bugs.freedesktop.org/show_bug.cgi?id=101867. Just pinging in to make sure we're aware, hopefully we'll have a fix cc'd within the week. Cheers, - Marc Di Luzio Linux Group Lead @ Feral Interactive Ltd. On 23 July 2017 at 05:49, Jason Ekstrand wrote: > On Fri, Jul 21, 2017 at 11:00 AM, Emil Velikov > wrote: > >> On 20 July 2017 at 06:09, Jason Ekstrand wrote: >> > On Mon, Jul 17, 2017 at 7:54 AM, Emil Velikov > > >> > wrote: >> >> >> >> On 16 July 2017 at 06:35, Jason Ekstrand wrote: >> >> > n Fri, Jul 7, 2017 at 11:07 AM, Emil Velikov < >> emil.l.veli...@gmail.com> >> >> > wrote: >> >> >> >> >> >> Hi all, >> >> >> >> >> >> As you may have noticed, for a little while now we've had the >> release >> >> >> plan on the mesa3d.org website [1]. >> >> >> >> >> >> Here is the current tentative schedule. >> >> >> >> >> >> Jul 21 2017 - Feature freeze/Release candidate 1 >> >> >> Jul 28 2017 - Release candidate 2 >> >> >> Aug 04 2017 - Release candidate 3 >> >> >> Aug 11 2017 - Release candidate 4/final release >> >> >> >> >> >> This gives us approximately 2 weeks to get new features in. >> >> >> >> >> >> As always, please let me know of must have features that you'll like >> >> >> to merge before the branch point. >> >> > >> >> > >> >> > Here's my wishlist: >> >> > >> >> > 1) I'd like to land the rest of Topi's work to convert the i965 >> driver >> >> > over >> >> > to ISL. I really don't want to have a release where it's half old >> >> > miptree >> >> > code and half ISL. That's going to make back-porting a real pain. >> > >> > >> > The depth/stencil bits are basically ready to land and I think Topi >> will be >> > sending the color bits later today. >> > > Landed. > > >> >> >> >> > 2) I've got a bunch of fixes to the miptree code that are currently >> WIP >> >> > that I'd like to see go in. If they don't make the branch point, >> I'll >> >> > probably just CC the lot to stable so it's not a huge deal. >> > >> > >> > These hit the list today. I expect topi to review fairly quickly. >> > > Landed. > > >> >> >> >> > 3) As many of the new Vulkan extensions as we can land. But don't >> >> > block >> >> > the release on any of those. >> > >> > >> > I think everything I had any hope of landing here has landed. >> > >> >> >> >> It's a bit lengthy list considering we have a bit less than a week. >> >> >> >> I've pushed my Vulkan fixes so you can merge the generator rework. >> >> I'll try to lend a hand for the rest. >> > >> > >> > If the branch got delayed by a couple of days to let the miptree churn >> land, >> > I wouldn't mind at all. Otherwise, I think there's a decent chance >> we'll be >> > CCing the whole thing to stable because we really don't want 17.2 to be >> half >> > ISL and half old code. >> > >> Taking into account the above and the a few outstanding build bits, >> let's call give it another couple of days. >> That will be Sunday late afternoon. I'll do a final shout out on IRC >> an hour or two in advance >> > > I've gotten everything in that I was hoping for. Thanks for the short > delay! > > --Jason > > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
On Fri, Jul 21, 2017 at 11:00 AM, Emil Velikov wrote: > On 20 July 2017 at 06:09, Jason Ekstrand wrote: > > On Mon, Jul 17, 2017 at 7:54 AM, Emil Velikov > > wrote: > >> > >> On 16 July 2017 at 06:35, Jason Ekstrand wrote: > >> > n Fri, Jul 7, 2017 at 11:07 AM, Emil Velikov < > emil.l.veli...@gmail.com> > >> > wrote: > >> >> > >> >> Hi all, > >> >> > >> >> As you may have noticed, for a little while now we've had the release > >> >> plan on the mesa3d.org website [1]. > >> >> > >> >> Here is the current tentative schedule. > >> >> > >> >> Jul 21 2017 - Feature freeze/Release candidate 1 > >> >> Jul 28 2017 - Release candidate 2 > >> >> Aug 04 2017 - Release candidate 3 > >> >> Aug 11 2017 - Release candidate 4/final release > >> >> > >> >> This gives us approximately 2 weeks to get new features in. > >> >> > >> >> As always, please let me know of must have features that you'll like > >> >> to merge before the branch point. > >> > > >> > > >> > Here's my wishlist: > >> > > >> > 1) I'd like to land the rest of Topi's work to convert the i965 > driver > >> > over > >> > to ISL. I really don't want to have a release where it's half old > >> > miptree > >> > code and half ISL. That's going to make back-porting a real pain. > > > > > > The depth/stencil bits are basically ready to land and I think Topi will > be > > sending the color bits later today. > Landed. > >> > >> > 2) I've got a bunch of fixes to the miptree code that are currently > WIP > >> > that I'd like to see go in. If they don't make the branch point, I'll > >> > probably just CC the lot to stable so it's not a huge deal. > > > > > > These hit the list today. I expect topi to review fairly quickly. > Landed. > >> > >> > 3) As many of the new Vulkan extensions as we can land. But don't > >> > block > >> > the release on any of those. > > > > > > I think everything I had any hope of landing here has landed. > > > >> > >> It's a bit lengthy list considering we have a bit less than a week. > >> > >> I've pushed my Vulkan fixes so you can merge the generator rework. > >> I'll try to lend a hand for the rest. > > > > > > If the branch got delayed by a couple of days to let the miptree churn > land, > > I wouldn't mind at all. Otherwise, I think there's a decent chance > we'll be > > CCing the whole thing to stable because we really don't want 17.2 to be > half > > ISL and half old code. > > > Taking into account the above and the a few outstanding build bits, > let's call give it another couple of days. > That will be Sunday late afternoon. I'll do a final shout out on IRC > an hour or two in advance > I've gotten everything in that I was hoping for. Thanks for the short delay! --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
On 20 July 2017 at 06:09, Jason Ekstrand wrote: > On Mon, Jul 17, 2017 at 7:54 AM, Emil Velikov > wrote: >> >> On 16 July 2017 at 06:35, Jason Ekstrand wrote: >> > n Fri, Jul 7, 2017 at 11:07 AM, Emil Velikov >> > wrote: >> >> >> >> Hi all, >> >> >> >> As you may have noticed, for a little while now we've had the release >> >> plan on the mesa3d.org website [1]. >> >> >> >> Here is the current tentative schedule. >> >> >> >> Jul 21 2017 - Feature freeze/Release candidate 1 >> >> Jul 28 2017 - Release candidate 2 >> >> Aug 04 2017 - Release candidate 3 >> >> Aug 11 2017 - Release candidate 4/final release >> >> >> >> This gives us approximately 2 weeks to get new features in. >> >> >> >> As always, please let me know of must have features that you'll like >> >> to merge before the branch point. >> > >> > >> > Here's my wishlist: >> > >> > 1) I'd like to land the rest of Topi's work to convert the i965 driver >> > over >> > to ISL. I really don't want to have a release where it's half old >> > miptree >> > code and half ISL. That's going to make back-porting a real pain. > > > The depth/stencil bits are basically ready to land and I think Topi will be > sending the color bits later today. > >> >> > 2) I've got a bunch of fixes to the miptree code that are currently WIP >> > that I'd like to see go in. If they don't make the branch point, I'll >> > probably just CC the lot to stable so it's not a huge deal. > > > These hit the list today. I expect topi to review fairly quickly. > >> >> > 3) As many of the new Vulkan extensions as we can land. But don't >> > block >> > the release on any of those. > > > I think everything I had any hope of landing here has landed. > >> >> It's a bit lengthy list considering we have a bit less than a week. >> >> I've pushed my Vulkan fixes so you can merge the generator rework. >> I'll try to lend a hand for the rest. > > > If the branch got delayed by a couple of days to let the miptree churn land, > I wouldn't mind at all. Otherwise, I think there's a decent chance we'll be > CCing the whole thing to stable because we really don't want 17.2 to be half > ISL and half old code. > Taking into account the above and the a few outstanding build bits, let's call give it another couple of days. That will be Sunday late afternoon. I'll do a final shout out on IRC an hour or two in advance. Thanks Emil ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
On Mon, Jul 17, 2017 at 7:54 AM, Emil Velikov wrote: > On 16 July 2017 at 06:35, Jason Ekstrand wrote: > > n Fri, Jul 7, 2017 at 11:07 AM, Emil Velikov > > wrote: > >> > >> Hi all, > >> > >> As you may have noticed, for a little while now we've had the release > >> plan on the mesa3d.org website [1]. > >> > >> Here is the current tentative schedule. > >> > >> Jul 21 2017 - Feature freeze/Release candidate 1 > >> Jul 28 2017 - Release candidate 2 > >> Aug 04 2017 - Release candidate 3 > >> Aug 11 2017 - Release candidate 4/final release > >> > >> This gives us approximately 2 weeks to get new features in. > >> > >> As always, please let me know of must have features that you'll like > >> to merge before the branch point. > > > > > > Here's my wishlist: > > > > 1) I'd like to land the rest of Topi's work to convert the i965 driver > over > > to ISL. I really don't want to have a release where it's half old > miptree > > code and half ISL. That's going to make back-porting a real pain. > The depth/stencil bits are basically ready to land and I think Topi will be sending the color bits later today. > > 2) I've got a bunch of fixes to the miptree code that are currently WIP > > that I'd like to see go in. If they don't make the branch point, I'll > > probably just CC the lot to stable so it's not a huge deal. > These hit the list today. I expect topi to review fairly quickly. > > 3) As many of the new Vulkan extensions as we can land. But don't block > > the release on any of those. > I think everything I had any hope of landing here has landed. > It's a bit lengthy list considering we have a bit less than a week. > > I've pushed my Vulkan fixes so you can merge the generator rework. > I'll try to lend a hand for the rest. > If the branch got delayed by a couple of days to let the miptree churn land, I wouldn't mind at all. Otherwise, I think there's a decent chance we'll be CCing the whole thing to stable because we really don't want 17.2 to be half ISL and half old code. --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
On 16 July 2017 at 06:35, Jason Ekstrand wrote: > n Fri, Jul 7, 2017 at 11:07 AM, Emil Velikov > wrote: >> >> Hi all, >> >> As you may have noticed, for a little while now we've had the release >> plan on the mesa3d.org website [1]. >> >> Here is the current tentative schedule. >> >> Jul 21 2017 - Feature freeze/Release candidate 1 >> Jul 28 2017 - Release candidate 2 >> Aug 04 2017 - Release candidate 3 >> Aug 11 2017 - Release candidate 4/final release >> >> This gives us approximately 2 weeks to get new features in. >> >> As always, please let me know of must have features that you'll like >> to merge before the branch point. > > > Here's my wishlist: > > 1) I'd like to land the rest of Topi's work to convert the i965 driver over > to ISL. I really don't want to have a release where it's half old miptree > code and half ISL. That's going to make back-porting a real pain. > > 2) I've got a bunch of fixes to the miptree code that are currently WIP > that I'd like to see go in. If they don't make the branch point, I'll > probably just CC the lot to stable so it's not a huge deal. > > 3) As many of the new Vulkan extensions as we can land. But don't block > the release on any of those. > It's a bit lengthy list considering we have a bit less than a week. I've pushed my Vulkan fixes so you can merge the generator rework. I'll try to lend a hand for the rest. Thanks Emil ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
n Fri, Jul 7, 2017 at 11:07 AM, Emil Velikov wrote: > Hi all, > > As you may have noticed, for a little while now we've had the release > plan on the mesa3d.org website [1]. > > Here is the current tentative schedule. > > Jul 21 2017 - Feature freeze/Release candidate 1 > Jul 28 2017 - Release candidate 2 > Aug 04 2017 - Release candidate 3 > Aug 11 2017 - Release candidate 4/final release > > This gives us approximately 2 weeks to get new features in. > > As always, please let me know of must have features that you'll like > to merge before the branch point. > Here's my wishlist: 1) I'd like to land the rest of Topi's work to convert the i965 driver over to ISL. I really don't want to have a release where it's half old miptree code and half ISL. That's going to make back-porting a real pain. 2) I've got a bunch of fixes to the miptree code that are currently WIP that I'd like to see go in. If they don't make the branch point, I'll probably just CC the lot to stable so it's not a huge deal. 3) As many of the new Vulkan extensions as we can land. But don't block the release on any of those. --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
On 12 July 2017 at 15:25, Lucas Stach wrote: > Hi Emil, > > Am Freitag, den 07.07.2017, 19:07 +0100 schrieb Emil Velikov: >> Hi all, >> >> As you may have noticed, for a little while now we've had the release >> plan on the mesa3d.org website [1]. >> >> Here is the current tentative schedule. >> >> Jul 21 2017 - Feature freeze/Release candidate 1 >> Jul 28 2017 - Release candidate 2 >> Aug 04 2017 - Release candidate 3 >> Aug 11 2017 - Release candidate 4/final release >> >> This gives us approximately 2 weeks to get new features in. >> >> As always, please let me know of must have features that you'll like >> to merge before the branch point. > > So here is my wishlist: > > 1. Daniel Stones series to use the zwp_linux_dmabuf protocol in the > EGL/wayland platform. > 2. My series enabling resource allocation/import/export with modifiers > on etnaviv. > > Both combined provide a working and performant Wayland implementation on > etnaviv, as well as allowing performance optimizations on the i.MX6 > QuadPlus. This would be a nice milestone to hit for etnaviv. > Fully agreed. I've skimmed again through Daniel's series and barring the odd small fix (or comment request) it looks good. I've thrown a few suggestions to add a `make check' test, but those can be looked at a later stage. Thanks Emil ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Mesa 17.2.0 release plan
Hi Emil, Am Freitag, den 07.07.2017, 19:07 +0100 schrieb Emil Velikov: > Hi all, > > As you may have noticed, for a little while now we've had the release > plan on the mesa3d.org website [1]. > > Here is the current tentative schedule. > > Jul 21 2017 - Feature freeze/Release candidate 1 > Jul 28 2017 - Release candidate 2 > Aug 04 2017 - Release candidate 3 > Aug 11 2017 - Release candidate 4/final release > > This gives us approximately 2 weeks to get new features in. > > As always, please let me know of must have features that you'll like > to merge before the branch point. So here is my wishlist: 1. Daniel Stones series to use the zwp_linux_dmabuf protocol in the EGL/wayland platform. 2. My series enabling resource allocation/import/export with modifiers on etnaviv. Both combined provide a working and performant Wayland implementation on etnaviv, as well as allowing performance optimizations on the i.MX6 QuadPlus. This would be a nice milestone to hit for etnaviv. Regards, Lucas ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev