From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
Bernd Kuhls <bernd@kuhls.net>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] package/mesa3d: bump to 24.2.0
Date: Thu, 22 Aug 2024 17:58:46 +0100 [thread overview]
Message-ID: <871q2gmr3t.fsf@draig.linaro.org> (raw)
In-Reply-To: <Zsdfx5CUXg8ARG75@landeda> (Yann E. MORIN's message of "Thu, 22 Aug 2024 17:56:55 +0200")
"Yann E. MORIN" <yann.morin.1998@free.fr> writes:
> Alex, All,
>
> On 2024-08-22 14:02 +0100, Alex Bennée spake thusly:
>> While VirtIO Venus support went in earlier this is the first version
>> that is known to work well.
>
> This commit log is confusing: it talks about VirtIO Venus, but there is
> no such addition in the patch.
Support for VirtIO venus was added in patch 1/4 but testing has shown it
needs at least 24.2.0 to work properly.
> It however adds a dependency on
> host-python-pyyaml, but that is not explained, and does not seem
> related
It was a dependency I needed to add to support the build.
> to VirtIO Venus either...
>
> Could you clarify, please?
>
> Also, see below...
>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> package/mesa3d-headers/mesa3d-headers.mk | 2 +-
>> package/mesa3d/mesa3d.hash | 5 ++---
>> package/mesa3d/mesa3d.mk | 3 ++-
>> 3 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/package/mesa3d-headers/mesa3d-headers.mk b/package/mesa3d-headers/mesa3d-headers.mk
>> index 33c60b285f..98afb77a9c 100644
>> --- a/package/mesa3d-headers/mesa3d-headers.mk
>> +++ b/package/mesa3d-headers/mesa3d-headers.mk
>> @@ -12,7 +12,7 @@ endif
>>
>> # Not possible to directly refer to mesa3d variables, because of
>> # first/second expansion trickery...
>> -MESA3D_HEADERS_VERSION = 24.0.9
>> +MESA3D_HEADERS_VERSION = 24.2.0
>> MESA3D_HEADERS_SOURCE = mesa-$(MESA3D_HEADERS_VERSION).tar.xz
>> MESA3D_HEADERS_SITE = https://archive.mesa3d.org
>> MESA3D_HEADERS_DL_SUBDIR = mesa3d
>> diff --git a/package/mesa3d/mesa3d.hash b/package/mesa3d/mesa3d.hash
>> index d506d398b8..1ff11f9bd8 100644
>> --- a/package/mesa3d/mesa3d.hash
>> +++ b/package/mesa3d/mesa3d.hash
>> @@ -1,5 +1,4 @@
>> -# From https://lists.freedesktop.org/archives/mesa-announce/2024-June/000764.html
>> -sha256 51aa686ca4060e38711a9e8f60c8f1efaa516baf411946ed7f2c265cd582ca4c mesa-24.0.9.tar.xz
>> -sha512 de2ee6c9df1fc106ee10befe0a76be1e9cfe83d65dbdb83bad6d8d7cfaa085232fb115293a1a790b37b50b1fe14bd58aafbcfe5a15e953b5901a7105d57569a5 mesa-24.0.9.tar.xz
>> +# From https://docs.mesa3d.org/relnotes/24.2.0.html
>> +sha256 c02bb72cea290f78b11895a0c95c7c92394f180d7ff66d4a762ec6950a58addf mesa-24.2.0.tar.xz
>
> There previously was sha256 _and_ sha512 hashes, but now you only add a
> sha256 one. Can you extend a little blurb about that, please?
Sure - only the sha256 was in the relase announcement. I could calculate
one if you want?
>
> Regards,
> Yann E. MORIN.
>
>> # License
>> sha256 a00275a53178e2645fb65be99a785c110513446a5071ff2c698ed260ad917d75 docs/license.rst
>> diff --git a/package/mesa3d/mesa3d.mk b/package/mesa3d/mesa3d.mk
>> index d3b5010648..29f26c5663 100644
>> --- a/package/mesa3d/mesa3d.mk
>> +++ b/package/mesa3d/mesa3d.mk
>> @@ -5,7 +5,7 @@
>> ################################################################################
>>
>> # When updating the version, please also update mesa3d-headers
>> -MESA3D_VERSION = 24.0.9
>> +MESA3D_VERSION = 24.2.0
>> MESA3D_SOURCE = mesa-$(MESA3D_VERSION).tar.xz
>> MESA3D_SITE = https://archive.mesa3d.org
>> MESA3D_LICENSE = MIT, SGI, Khronos
>> @@ -21,6 +21,7 @@ MESA3D_DEPENDENCIES = \
>> host-bison \
>> host-flex \
>> host-python-mako \
>> + host-python-pyyaml \
>> expat \
>> libdrm \
>> zlib
>> --
>> 2.39.2
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-22 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 13:02 [Buildroot] [PATCH 0/4] Update Mesa and enable vkmark Alex Bennée
2024-08-22 13:02 ` [Buildroot] [PATCH 1/4] package/mesa3d: add option to enable VIRTIO vulkan driver Alex Bennée
2024-08-22 13:02 ` [Buildroot] [PATCH 2/4] package/vkmark: add vmkark benchmarking tool Alex Bennée
2024-08-23 17:26 ` Thomas Petazzoni via buildroot
2024-08-22 13:02 ` [Buildroot] [PATCH 3/4] board/qemu: add post-build script to aarch64_virt_defconfig Alex Bennée
2024-08-23 17:27 ` Thomas Petazzoni via buildroot
2024-08-22 13:02 ` [Buildroot] [PATCH 4/4] package/mesa3d: bump to 24.2.0 Alex Bennée
2024-08-22 15:56 ` Yann E. MORIN
2024-08-22 16:58 ` Alex Bennée [this message]
2024-08-22 17:24 ` Yann E. MORIN
2024-08-22 19:41 ` Alex Bennée
2024-08-22 20:02 ` Yann E. MORIN
2024-08-22 17:25 ` [Buildroot] [PATCH 0/4] Update Mesa and enable vkmark Alex Bennée
[not found] ` <20240822130220.4135741-5-alex.bennee__3974.23927658878$1724331783$gmane$org@linaro.org>
2024-08-22 17:59 ` [Buildroot] [PATCH 4/4] package/mesa3d: bump to 24.2.0 Bernd Kuhls
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=871q2gmr3t.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=yann.morin.1998@free.fr \
/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