Mesa has removed swrast https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST Any help would be grateful so TW can receive the latest Mesa, as weel as it's new features. GL_EXT_demote_to_helper_invocation on radeonsi GL_NV_compute_shader_derivatives on radeonsi EGL_MESA_platform_xcb Removed GL_NV_point_sprite for classic swrast. driconf: remove glx_disable_oml_sync_control, glx_disable_sgi_video_sync, and glx_disable_ext_buffer_age Removed support for loading DRI drivers older than Mesa 8.0, including all DRI1 support Add support for VK_VALVE_mutable_descriptor_type on RADV Removed classic OSMesa in favor of the newly improved gallium OSMesa VK_KHR_fragment_shading_rate on RADV (RDNA2 only) Freedreno a6xx exposes GL 3.3 Classic swrast dri driver removed in favor of gallium swrast (llvmpipe or softpipe) Panfrost g31/g52/g72 exposes ES 3.0 Panfrost t760+ exposes GL 3.1 (including on Bifrost) Sparse memory support on RADV Rapid packed math (16bit-vectorization) on RADV Sent with [ProtonMail](https://protonmail.com) Secure Email.
On 4/15/21 4:14 PM, Aaron wrote:
Mesa has removed swrast https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST
Jackson noted, "Following up from the classic swrast OSMesa removal in favor of llvmpipe/softpipe, remove the classic swrast DRI driver. It's unused by any distribution -- debian was the last holdout until this week, which had it enabled instead of softpipe on obscure platforms (non-LLVM and hurd). Now that debian has switched, remove the driver so nobody can accidentally enable it again."
Hmm, so if I understand correctly, if a target doesn't have an LLVM backend at the moment, we can still use softpipe, can't we? I'll need to talk with upstream about that. Adrian
Am 15.04.21 um 16:14 schrieb Aaron:
Mesa has removed swrast https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST
Any help would be grateful so TW can receive the latest Mesa, as weel as it's new features.
I would assume that Stefan Dirsch is already working on Mesa 21. I'd welcome it because the current Mesa in Tumbleweed looks like it would need quite a number of patches for LLVM 12. (I haven't even tried, I'm running 21.0.1 with two patches right now.) Best regards, Aaron
On Thu, Apr 15, 2021 at 11:42:29PM +0200, Aaron Puchert wrote:
Am 15.04.21 um 16:14 schrieb Aaron:
Mesa has removed swrast https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST
Any help would be grateful so TW can receive the latest Mesa, as weel as it's new features.
I would assume that Stefan Dirsch is already working on Mesa 21.
Tried once. Gave up after 2 hours fiddling around with meson options, when other things popped up with higher severity and priority. Can't say for sure, but I expect this to be a task for several days to get the update done. :-(
I'd welcome it because the current Mesa in Tumbleweed looks like it would need quite a number of patches for LLVM 12. (I haven't even tried,
Ok. So an update to LLVM12 is already in the works?
I'm running 21.0.1 with two patches right now.)
Interesting. Is this on openSUSE with our Mesa package and your changes/patches on top of it? Or did you build Mesa 21 manually? Anyway, help with the Mesa update to version 21 would be appreciated. ;-) Thanks, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ---------------------------------------------------------------- (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer ----------------------------------------------------------------
Hi all, On 16.04.21 12:01, Stefan Dirsch wrote:
On Thu, Apr 15, 2021 at 11:42:29PM +0200, Aaron Puchert wrote:
Am 15.04.21 um 16:14 schrieb Aaron:
Mesa has removed swrast https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST
Any help would be grateful so TW can receive the latest Mesa, as weel as it's new features. I would assume that Stefan Dirsch is already working on Mesa 21. Tried once. Gave up after 2 hours fiddling around with meson options, when other things popped up with higher severity and priority. Can't say for sure, but I expect this to be a task for several days to get the update done. :-(
I have an unstable Mesa git snapshot package in my home project which is base on X11:XOrg (concenering the packaging), it may help with the initial update. Lets see if i find the time to push a first version of Mesa 21.0 to X11:XOrg this weekend.
I'd welcome it because the current Mesa in Tumbleweed looks like it would need quite a number of patches for LLVM 12. (I haven't even tried, Ok. So an update to LLVM12 is already in the works?
I'm running 21.0.1 with two patches right now.) Interesting. Is this on openSUSE with our Mesa package and your changes/patches on top of it? Or did you build Mesa 21 manually? Anyway, help with the Mesa update to version 21 would be appreciated. ;-)
Thanks, Stefan
Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ---------------------------------------------------------------- (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer ----------------------------------------------------------------
On Fri, Apr 16, 2021 at 08:29:51PM +0200, Tobias Klausmann wrote:
Hi all,
On 16.04.21 12:01, Stefan Dirsch wrote:
On Thu, Apr 15, 2021 at 11:42:29PM +0200, Aaron Puchert wrote:
Am 15.04.21 um 16:14 schrieb Aaron:
Mesa has removed swrast https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST
Any help would be grateful so TW can receive the latest Mesa, as weel as it's new features. I would assume that Stefan Dirsch is already working on Mesa 21. Tried once. Gave up after 2 hours fiddling around with meson options, when other things popped up with higher severity and priority. Can't say for sure, but I expect this to be a task for several days to get the update done. :-(
I have an unstable Mesa git snapshot package in my home project which is base on X11:XOrg (concenering the packaging), it may help with the initial update. Lets see if i find the time to push a first version of Mesa 21.0 to X11:XOrg this weekend.
Thanks a lot! That would be great! :-) CU, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ---------------------------------------------------------------- (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer ----------------------------------------------------------------
Am 16.04.21 um 12:01 schrieb Stefan Dirsch:
Tried once. Gave up after 2 hours fiddling around with meson options, when other things popped up with higher severity and priority. Can't say for sure, but I expect this to be a task for several days to get the update done. :-(
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option. A bigger problem is osmesa. First of all the configuration options changed, so instead of classic/none we have now true/false. I tried going with -Dosmesa=true in Mesa and -Dosmesa=false in Mesa-drivers but that didn't work out because it apparently wants softpipe or llvmpipe which we don't build in Mesa. So I moved it to Mesa-drivers. Not sure if we want that, perhaps there is a better solution. Other than that I've just ported back two Clover changes for LLVM 12.
Ok. So an update to LLVM12 is already in the works?
Yes, I package LLVM release candidates early on so that I can report issues upstream. It's more or less ready now, I just want to replace one patch by the proper upstream fix.
I'm running 21.0.1 with two patches right now.) Interesting. Is this on openSUSE with our Mesa package and your changes/patches on top of it? Or did you build Mesa 21 manually? Anyway, help with the Mesa update to version 21 would be appreciated. ;-)
It's all in https://build.opensuse.org/project/show/home:aaronpuchert:llvm-next but I'll need to polish it a bit before I submit the changes. I wasn't planning on doing the actual Mesa update, but if needed I guess I can do it along the way. Best regards, Aaron
On Fri, Apr 16, 2021 at 11:57:34PM +0200, Aaron Puchert wrote:
Am 16.04.21 um 12:01 schrieb Stefan Dirsch:
Tried once. Gave up after 2 hours fiddling around with meson options, when other things popped up with higher severity and priority. Can't say for sure, but I expect this to be a task for several days to get the update done. :-(
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option.
Yes, that's one of the issues here. I'm afraid things will get difficult on platforms without any hardware driver. :-( But I will have a try with "auto" or removing this option completely on such platforms. Let's see ...
A bigger problem is osmesa. First of all the configuration options changed, so instead of classic/none we have now true/false. I tried going with -Dosmesa=true in Mesa and -Dosmesa=false in Mesa-drivers but that didn't work out because it apparently wants softpipe or llvmpipe which we don't build in Mesa. So I moved it to Mesa-drivers. Not sure if we want that, perhaps there is a better solution.
I think that's a good idea. Currently working on it.
Other than that I've just ported back two Clover changes for LLVM 12.
Ok. That's something for later. ;-)
Ok. So an update to LLVM12 is already in the works?
Yes, I package LLVM release candidates early on so that I can report issues upstream. It's more or less ready now, I just want to replace one patch by the proper upstream fix.
I see. Thanks for doing this!
I'm running 21.0.1 with two patches right now.) Interesting. Is this on openSUSE with our Mesa package and your changes/patches on top of it? Or did you build Mesa 21 manually? Anyway, help with the Mesa update to version 21 would be appreciated. ;-)
It's all in https://build.opensuse.org/project/show/home:aaronpuchert:llvm-next but I'll need to polish it a bit before I submit the changes. I wasn't planning on doing the actual Mesa update, but if needed I guess I can do it along the way.
Probably not needed. Things are looking good right now. I expect biggest issues on platforms without hardware driver like s390, ppc64, etc. Thanks, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ---------------------------------------------------------------- (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer ----------------------------------------------------------------
On Saturday 2021-04-17 12:32, Stefan Dirsch wrote:
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option.
Yes, that's one of the issues here. I'm afraid things will get difficult on platforms without any hardware driver. :-(
Can llvmpipe take the role of software rasterization?
On Sat, Apr 17, 2021 at 01:18:40PM +0200, Jan Engelhardt wrote:
On Saturday 2021-04-17 12:32, Stefan Dirsch wrote:
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option.
Yes, that's one of the issues here. I'm afraid things will get difficult on platforms without any hardware driver. :-(
Can llvmpipe take the role of software rasterization?
Just received a submit by Tobias, which probably fixes that issue. Thanks, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ---------------------------------------------------------------- (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer ----------------------------------------------------------------
Am 17.04.21 um 15:29 schrieb Stefan Dirsch:
On Sat, Apr 17, 2021 at 01:18:40PM +0200, Jan Engelhardt wrote:
On Saturday 2021-04-17 12:32, Stefan Dirsch wrote:
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option.
Yes, that's one of the issues here. I'm afraid things will get difficult on platforms without any hardware driver. :-(
Can llvmpipe take the role of software rasterization?
Just received a submit by Tobias, which probably fixes that issue.
Using a gallium driver makes Mesa a larger build (about 1000 files to compile instead of 800), but it appears with that change you can move osmesa back from Mesa-drivers to Mesa. So you can probably undo most of the changes for that. (Just tried it out in my repo.) Since I guess the main point of the split is to have the libraries without LLVM already I think the slightly larger build should be Ok. Best regards, Aaron
On Sat, Apr 17, 2021 at 06:52:21PM +0200, Aaron Puchert wrote:
Am 17.04.21 um 15:29 schrieb Stefan Dirsch:
On Sat, Apr 17, 2021 at 01:18:40PM +0200, Jan Engelhardt wrote:
On Saturday 2021-04-17 12:32, Stefan Dirsch wrote:
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option.
Yes, that's one of the issues here. I'm afraid things will get difficult on platforms without any hardware driver. :-(
Can llvmpipe take the role of software rasterization?
Just received a submit by Tobias, which probably fixes that issue.
Using a gallium driver makes Mesa a larger build (about 1000 files to compile instead of 800), but it appears with that change you can move osmesa back from Mesa-drivers to Mesa. So you can probably undo most of the changes for that. (Just tried it out in my repo.)
Since I guess the main point of the split is to have the libraries without LLVM already I think the slightly larger build should be Ok.
Yes, indeed. Thanks for the new submit! Already accepted. Looks good so far. Also on the non-x86_64 platforms! CU, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ---------------------------------------------------------------- (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer ----------------------------------------------------------------
On 17.04.21 18:52, Aaron Puchert wrote:
Am 17.04.21 um 15:29 schrieb Stefan Dirsch:
On Sat, Apr 17, 2021 at 01:18:40PM +0200, Jan Engelhardt wrote:
On Saturday 2021-04-17 12:32, Stefan Dirsch wrote:
One problem is that swrast is gone and you've used that as "alibi" driver in the Mesa package (the actual drivers are all built in Mesa-drivers). I've replaced it with nouveau, but maybe there is a better option.
Yes, that's one of the issues here. I'm afraid things will get difficult on platforms without any hardware driver. :-(
Can llvmpipe take the role of software rasterization?
Just received a submit by Tobias, which probably fixes that issue.
Using a gallium driver makes Mesa a larger build (about 1000 files to compile instead of 800),
Hmm strange...for me it makes the build smaller 1200 -> 1000 items and when it comes to build times 208 -> 152 seconds for a local "osc build". Which arch are you building?
but it appears with that change you can move osmesa back from Mesa-drivers to Mesa. So you can probably undo most of the changes for that. (Just tried it out in my repo.)
Since I guess the main point of the split is to have the libraries without LLVM already I think the slightly larger build should be Ok.
Best regards, Aaron
Am 17.04.21 um 22:29 schrieb Tobias Klausmann:
On 17.04.21 18:52, Aaron Puchert wrote:
Using a gallium driver makes Mesa a larger build (about 1000 files to compile instead of 800),
Hmm strange...for me it makes the build smaller 1200 -> 1000 items and when it comes to build times 208 -> 152 seconds for a local "osc build".
Which arch are you building?
That's on x86_64, but I was using -Ddri-drivers=nouveau previously instead of -Dgallium-drivers=swrast. We're throwing away the driver anyway so it doesn't really matter. (Note the rm -f %{buildroot}/%{_libdir}/dri/*_dri.so.) But that meant we couldn't have osmesa in Mesa, so I think your solution is preferable. Best regards, Aaron
participants (6)
-
Aaron -
Aaron Puchert -
Jan Engelhardt -
John Paul Adrian Glaubitz -
Stefan Dirsch -
Tobias Klausmann