Currently chromium vaapi backend using the hardcoded path "/dev/dri/renderD128" for opening the drm handle. This should work for Intel chromebooks but may not be true for a machine having multiple GPUs (for eg: an IA based linux host which has a discrete Nvidia gpu). Another use case I can think of is a Chromebook which uses mesa gallium backend for Radeon gpu.

We may use udev apis for to this:
eg: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/commit/b622d21d6a309e3fdf698d9edb60d2f7423fd47f

Not a high priority item, but creating this to track missing features in vaapi backend.