Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15736] New: Mesa3D is missing H.264/H.265 support
Date: Tue, 22 Aug 2023 03:58:01 +0000	[thread overview]
Message-ID: <bug-15736-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15736

            Bug ID: 15736
           Summary: Mesa3D is missing H.264/H.265 support
           Product: buildroot
           Version: 2023.05.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: tristan.van.berkom@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

The codecs built into mesa are useful via `libva` and we are using via
`gst1-vaapi` in order to run gstreamer pipelines with hardware accelerated
decoding.

These codecs are now disabled by default in upstream mesa as per:
 
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7d969fe9e91e39e03041cdfac69bf33337bc2c96

And must be enabled via the new `Dvideo-codecs=` meson option.

A patch was submitted for this earlier this month:
  https://lists.buildroot.org/pipermail/buildroot/2023-August/671934.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-08-22  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  3:58 bugzilla [this message]
2023-08-22  5:49 ` [Buildroot] [Bug 15736] Mesa3D is missing H.264/H.265 support bugzilla

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=bug-15736-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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