> Not sure I get your point, you mean I find a way to identity the va driver path during gyp time?

My point is: libva knows where to look (path) and what to look (driver .so name). We could make do the same.

As you said, where to look is a build time business. I found out we can get the driver path with ``pkgconfig``, so we could have this wrapped in on our buildsystem like we do for other Linux dependencies:
```
$ pkg-config libva --variable=driverdir
/usr/lib/x86_64-linux-gnu/dri
```
Now, the problem is: what driver to load?  I had a look at the VA code and apparently what it does is it asks the backend (say X11) for the driver name. In this case I'm fine with hardcoding i965*.