VA API on GM45

VA API on GM45

[Dmitry Nezhevenko]

Hi.

I've finally tried to use VA API on my GM45-based laptop and got followed:

--
libva: libva version 0.31.1
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/i965_drv_video.so
libva: va_openDriver() returns 0
[0x9a0cb94] avcodec decoder: Using VA API version 0.31 for hardware
decoding.
vlc: i965_avc_ildb.c:621: i965_avc_ildb_decode_init: Assertion
`avc_ildb_context->urb.cs_start + avc_ildb_context->urb.num_cs_entries *
avc_ildb_context->urb.size_cs_entry <= ((((&i965->intel)->device_id ==
0x0042) || ((&i965->intel)->device_id == 0x0046)) ? 1024 :
(((&i965->intel)->device_id == 0x2E02 || (&i965->intel)->device_id ==
0x2E12 || (&i965->intel)->device_id == 0x2E22 || (&i965->intel)->device_id
== 0x2E32) || ((&i965->intel)->device_id == 0x2A42)) ? 384 : 256)' failed.
--

System is mostly debian unstable (with everything va-related from
experimental). Google shows some discussions that asks to wait for Q3
drivers. 

I've looked to libva 1.0.5 package and this assert still presents in code.
So is VA API supported for GM45? 

Any other suggestions?

-- 
WBR, Dmitry

Re: VA API on GM45

[Niccolò Belli]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 03/10/2010 13:22, Dmitry Nezhevenko ha scritto:
> So is VA API supported for GM45? 

I don't think so, but it should have been available since September
according to the plans...

Darkbasic
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMqRKWAAoJEGTnL3tULjr4zh0H/1tgoo5RjChxXLlsO2bHVmaX
KMSfkjvU1EbrQV2fxgN0JslFxnG+W1czR5EJ7A3ybAi90lWpl7UMx3I8f6kXMsgG
KOgw7kXvK1JATd9JpVQQ6MZUmk7gyHScynMTUnwySqaVq5e35TcQGtOnEBT2HMzk
rfc043Po/+hr+UMI3y0okwWZMLDWc6XuolYPUg93gEEnHl0W1QaOqCotShMEP6kj
SkUCsBSfmKJcIeVsSLxmNtW5QKtn05TeYGF5/F5kwiFqYPIK3zRrhnoGKBO6SBv8
7xsc8ehLdFKiT6+YsbFu1+abrexCOHwOL/+ibd+wSakwMEhRoOU3rKKBSU+p/Eg=
=p2L8
-----END PGP SIGNATURE-----

Re: VA API on GM45

[Vittorio Mori]

Dmitry Nezhevenko <dion <at> inhex.net> writes:

> 
> 
> Hi.
> 
> I've finally tried to use VA API on my GM45-based laptop and got followed:

Exactly the same situation as yours here. Laptop: Acer extensa 5635, GM45 
chipset (Intel X4500MHD).

What I did:

- freshly installed Ubuntu 10.10rc

- got the latest packages from xorg-edgers ppa (to get a working vaapi 
implementation)

- vainfo reports:

libva: libva version 0.31.1
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/i965_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA API version: 0.31
vainfo: Driver version: i965 Driver 0.1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointVLD


- followed instructions (a little outdated) here : 
http://wiki.videolan.org/VLC_VAAPI

- got ffmpeg from git
- got vlc from git


When I launch VLC I get same assert fail as yours:

libva: libva version 0.31.1
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/i965_drv_video.so
libva: va_openDriver() returns 0
[0x2a0ee40] avcodec decoder: Using VA API version 0.31 for hardware decoding.
vlc: i965_avc_ildb.c:621: i965_avc_ildb_decode_init: Asserzione 
"avc_ildb_context->urb.cs_start + avc_ildb_context->urb.num_cs_entries * 
avc_ildb_context->urb.size_cs_entry <= ((((&i965->intel)->device_id == 0x0042) 
|| ((&i965->intel)->device_id == 0x0046)) ? 1024 : (((&i965->intel)->device_id 
== 0x2E02 || (&i965->intel)->device_id == 0x2E12 || (&i965->intel)->device_id == 
0x2E22 || (&i965->intel)->device_id == 0x2E32) || ((&i965->intel)->device_id == 
0x2A42)) ? 384 : 256)" non riuscita.
Aborted


I compiled mplayer-vaapi from scratch, but I get "Error opening/initializing the 
selected video_out (-vo) device.".

I guess it's still a work in progress, I've read thousands of posts and info on 
this subject (intel & vaapi), and I conclude that everything is still very messy 
and "fluid". It seems older chipsets (Cantiga) get, pretty obviously, lower 
piority. Most of the work is for the Clarkdale chipset.