From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
"huykhacnguyen1983@gmail.com" <huykhacnguyen1983@gmail.com>
Subject: Re: [yocto][chromium] Need support to enable intel VAAPI with Chromium
Date: Wed, 7 Jun 2023 01:49:12 +0000 [thread overview]
Message-ID: <0028e972a327c914b1cb7979ba8fd82bb2e103a4.camel@intel.com> (raw)
In-Reply-To: <CA+gF+GmO=MJWUzhpmw5J7DoixHkOOcBqNr2f7A2LZe_+FUnOcQ@mail.gmail.com>
On Wed, 2023-06-07 at 08:24 +0700, HuyK wrote:
> Hi all,
>
> I am working on Intel J4125 platform with these meta layers:
> - poky: master branch
> - meta-intel: master branch
> - meta-browser: master branch
>
> 1/ I build chromium by chromium-ozone-wayland_111.0.5563.147.bb
> recipe with adding "use-vaapi" and "proprietary-codecs" to
> PACKAGECONFI in chromium-gn.inc
> That chromium did not call intel VAAPI functions, but I see it
> loads iHD_drv_video.so at runtime.
>
> 2/ Then I research to find this link about applying patches to
> support VAAPI in
> chromium https://aur.archlinux.org/packages/chromium-wayland-vaapi
> + 0001-ozone-wayland-add-VA-API-support.patch
> + vaapi-add-av1-support.patch
> + use-oauth2-client-switches-as-default.patch
> This chromium loads iHD_drv_video.so and calls Intel VAAPI APIs;
> however, chromium reports these errors when I open to play an H264
> video so that HW Acceleration is not working
>
> [13436:13436:0606/150528.263552:ERROR:vaapi_wrapper.cc(2399)]
> vaCreateSurfaces (import mode) failed, VA error: resource allocation
> failed
> [13436:13436:0606/150528.263789:ERROR:vaapi_picture_native_pixmap_ozo
> ne.cc(73)] Failed creating VASurface for NativePixmap
> [13436:13436:0606/150528.264843:ERROR:vaapi_wrapper.cc(2399)]
> vaCreateSurfaces (import mode) failed, VA error: resource allocation
> failed
> [13436:13436:0606/150528.265073:ERROR:vaapi_picture_native_pixmap_ozo
> ne.cc(73)] Failed creating VASurface for NativePixmap
> [13436:13436:0606/150528.265294:VERBOSE1:vaapi_video_decode_accelerat
> or.cc(142)] NotifyError(): Notifying of error 4
This doesn't look like complete error log. A complete log would have
helped.
>
> So far, I could not find a solution to fix chromium errors and I am
> new to chromium, intel vaapi, libva debugging.
>
> Please support how to debug the errors there or guidance on how to
> officially build chromium with intel VAAPI support in Yocto?
This doesn't seem to be Yocto related. This looks very similar so
please try the suggestions here:
https://github.com/intel/media-driver/issues/1498
Thanks,
Anuj
next prev parent reply other threads:[~2023-06-07 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 1:24 [yocto][chromium] Need support to enable intel VAAPI with Chromium huy nguyen
2023-06-07 1:49 ` Mittal, Anuj [this message]
2023-06-07 1:57 ` huy nguyen
[not found] ` <17663DD3817D729F.23186@lists.yoctoproject.org>
2023-06-07 12:37 ` huy nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0028e972a327c914b1cb7979ba8fd82bb2e103a4.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=huykhacnguyen1983@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).