3 ms·
AMD not even ready for the Linux support yet? that's disappointing.
by ekianjo 3y ago
AMD not even ready for the Linux support yet? that's disappointing.
- jauntywundrkind 3y agoNot sure why this release is so slanted, but av1 encode on AMD Linux has been available since October. https://www.phoronix.com/news/Mesa-23.3-HQ-AV1-Radeon https://www.phoronix.com/news/Mesa-23.3-HQ-AV1-Radeon How Nvidia managed to emerge looking good on this PR is a colossal surprise & fucked up-ed-ly inappropriate.
- shmerl 3y agoI suppose the above comment was about amdvlk. radv is indeed often ahead of it these days. If anything, I think AMD should drop amdvlk on Linux (to collaborate on radv there) and instead try to develop radv for Windows if that's doable to replace amdvlk altogether.
- brucethemoose2 3y agoYeah. What even is the of keeping things split? RADV even has big commercial customers now (Valve).
- kimixa 3y agoMany of the people working on RADV are already employed by AMD (or paid by them indirectly), so arguably it's already collaborating. I see the amdvlk/radv drivers a bit like the windows "Radeon Pro"/"Adrenalin" driver split, one is for people who stare at solidworks all day, the other for everyone else.
- shmerl 3y agoI think AMD wanted to phase out that distinction for OpenGL for example, so why wouldn't they want the same for Vulkan There is no need for them to be different really in that sense. amdvlk and radv exist for historic reasons since they started independently and amdvlk was designed to support Windows too. But today I don't really see a big point in admvlk except where radv doesn't exist. So AMD can do what Intel does. Support radv on Linux and amdvlk on Windows for example, or as above, try to make radv work on Windows too.
- aaomidi 3y agoAnd meanwhile Chrome outright refuses to support vaapi outside of intel (and thats only because of chromebooks).
- Vogtinator 3y agoWith the right Mesa patch (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26165 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26...) and chromium flags to force enable vaapi, I've got working HW decode with amdgpu here.
- jauntywundrkind 3y agoSeems like with av1, Google had to stop self-sabotaging (turning on va-api has worked for most users for more than half a decade) & kind of had to move (because av1 is too beastly to do on cpu). Sounds like va-api has been turned on for almost a month now, but I haven't confirmed. https://www.phoronix.com/news/Google-Chrome-Wayland-VA-API https://www.phoronix.com/news/Google-Chrome-Wayland-VA-API Maybe I'm missing something, but from what I could dig up it sounds like Firefox only enables va-api on Intel. https://www.phoronix.com/news/Mozilla-Firefox-115 https://www.phoronix.com/news/Mozilla-Firefox-115
- rasz 3y agoAMD AV1 encoder is really bad, you arent missing much. https://goughlui.com/2023/12/31/video-codec-round-up-2023-part-11-hevc_amf-h-265-amd-advanced-media-framework/ https://goughlui.com/2023/12/31/video-codec-round-up-2023-pa... https://goughlui.com/2024/01/07/video-codec-round-up-2023-part-14-av1_amf-av1-amd-advanced-media-framework/ https://goughlui.com/2024/01/07/video-codec-round-up-2023-pa...
- emersion 3y agohttps://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27424 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27...