Spec URL: https://dl.kwizart.net/review/vaapi-tegra-driver.spec SRPM URL: https://dl.kwizart.net/review/vaapi-tegra-driver-0-0.620211020git49a56d3.fc35.src.rpm Description: Tegra VAAPI backend Fedora Account System Username: kwizart This package is only relevant on Nvidia Tegra architectures (armv7hl and aarch64) So far, upstream only has tested tegra196 and tegra184 but tegra210 should works (with some dts patches I'm working on). Build succeeded on copr: https://copr.fedorainfracloud.org/coprs/kwizart/tegra-nouveau/build/2961335/ This requires a very recent kernel. (it should have been 5.16-rc1, but it seems the PR was delayed, so it could be a later rc or 5.17).
Correction, this package is only relevant on aarch64. armv7hl SOC doesn't have the same HW layout. (I wonder if running armv7 userspace on jetson is possible like done in the rpi cases). Anyway, I will assume aarch64 here.
It seems upstream has not made a change for a year. Is this still wanted to be reviewed? Since we have more recent kernels in F37+, it should be easy to test. Is it still useful for users?
Thanks for looking into this. I'm afraid that this component is not ready. As such it only allows to decode h264 which might be encumbered (fedora has disabled mesa-va-drivers recently). Also I'm not sure if this ever worked with Wayland (might be) but I only have a Jetson-TX1 to test and unfortunately this doesn't yet work as it. Even with custom device-tree patches the device experiences hardlocks (might work with newer Tegra devices). So I'm going to import it in RPM Fusion free for now and leave this bug open but with NotReady...
I would actually close this, in it's current state I'm not sure this makes sense.