From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Gary Bisson <gary.bisson@boundarydevices.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/freescale-imx/imx-vpu-hantro: bump version to 1.27.0
Date: Thu, 24 Nov 2022 22:55:34 +0100 [thread overview]
Message-ID: <20221124225534.5c8867f0@windsurf> (raw)
In-Reply-To: <20221116091248.755689-1-gary.bisson@boundarydevices.com>
On Wed, 16 Nov 2022 10:12:48 +0100
Gary Bisson <gary.bisson@boundarydevices.com> wrote:
> - Same version as NXP release 5.15.52_2.1.0
> - EULA/COPYING: update to LA_OPT_NXP_Software_License v39
> - No official changelog but the main addition is the support of skipped
> h.264 frames
> - Add patch to fix kernel version test from the package
> - Yocto doesn't need that workaround as it installs the kernel headers
> - This is needed for NXP 5.15+ kernels (using DMABUF)
>
> Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> ---
> ...0003-Fix-Linux-kernel-version-header.patch | 45 +++++++++++++++++++
> .../imx-vpu-hantro/imx-vpu-hantro.hash | 6 +--
> .../imx-vpu-hantro/imx-vpu-hantro.mk | 2 +-
> 3 files changed, 49 insertions(+), 4 deletions(-)
> create mode 100644 package/freescale-imx/imx-vpu-hantro/0003-Fix-Linux-kernel-version-header.patch
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-24 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 9:12 [Buildroot] [PATCH] package/freescale-imx/imx-vpu-hantro: bump version to 1.27.0 Gary Bisson
2022-11-24 21:55 ` 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=20221124225534.5c8867f0@windsurf \
--to=buildroot@buildroot.org \
--cc=gary.bisson@boundarydevices.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.