> pkg-config gives just name or just path?

Just the parent path, for Ubunt64 instance, it gives `/usr/lib/x86_64-linux-gnu/dri/`

> with thiago's "solution", wouldn't we hardcode less? maybe it is totally acceptable.

Not really, the drivername still need to be determined, call `vaGetDriverName` is only workable way other than hard code. But as I said, it make no improvement than call `vaInitialize()`

> xwalk doesn't target desktop yet, so we dont really care, but making such a fix for linux in general (upstream) would be of good benefit.

Yes, I've tried. http://crrev.com/176883018 and https://crrev.com/16430003/ are trying do the same thing. But upstream attitude is not changed yet, they only want to support ChromeOS.  If one of them get acceptted, this PR could be upstreamed.

> does thiago want to pursue such a change upstream?

Again, upstream does not want to enable libva for linux in general

> Can we just hardcode for IVI ? avoiding performance disadvantage

Yes, That is the alternative solution I offered. If we only want support Tizen (IVI or Mobile) the patch should be very simple that hard coded va driver path protected with `OS_TIZEN` macro. Do we really set the goal that support Tizen only? @kenchris please make a decision.