It's probably better to focus more on Intel until everything is working well enough to close the bug. VAAPI has historically only been reliable on Intel so we risk getting distracted in debugging non-Intel driver issues (which would also be off-topic given this is a Chromium bug).
It's probably better to focus more on Intel until everything is working well enough to close the bug. VAAPI has historically only been reliable on Intel so we risk getting distracted in debugging non-Intel driver issues (which would also be off-topic given this is a Chromium bug).