From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/libva-intel-driver: bump version to 2.4.5
Date: Sat, 8 Aug 2026 20:26:21 +0200 [thread overview]
Message-ID: <and0wgX3tpnbQGBD@windsurf> (raw)
In-Reply-To: <20260705182016.3258983-1-bernd@kuhls.net>
On Sun, Jul 05, 2026 at 08:20:16PM +0200, Bernd Kuhls wrote:
> https://github.com/irql-notlessorequal/intel-vaapi-driver/blob/2.4.5/NEWS
>
> This bump follows
> https://github.com/LibreELEC/LibreELEC.tv/commit/39d2ff612fce9bb57c43ac767df15052a896e9ed
>
> "Intel archived intel/intel-vaapi-driver at 2.4.1 and advises forking.
> irql-notlessorequal/intel-vaapi-driver is the active continuation (119
> commits ahead, tagged releases, Chromium fixes), so track it at 2.4.5.
> [...]
> The fork renamed the wayland meson option, so switch with_wayland to
> with_wayland_drm in all DISPLAYSERVER branches. Also drop the dead
> 01.org PKG_SITE."
>
> Updated license file and hash due to upstream commit:
> https://github.com/irql-notlessorequal/intel-vaapi-driver/commit/7343767d87926d519f528db88ba1edfb153d8289
>
> Also switch build system to meson.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master, thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-08 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 18:20 [Buildroot] [PATCH 1/1] package/libva-intel-driver: bump version to 2.4.5 Bernd Kuhls
2026-08-08 18:26 ` Thomas Petazzoni via buildroot [this message]
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=and0wgX3tpnbQGBD@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=eric.le.bihan.dev@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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