From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Alex Bennée" <alex.bennee@linaro.org>
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 22:02:00 +0200 [thread overview]
Message-ID: <ZseZOEB4XJ0a93P-@landeda> (raw)
In-Reply-To: <87seuwl501.fsf@draig.linaro.org>
Alex, All,
On 2024-08-22 20:41 +0100, Alex Bennée spake thusly:
> "Yann E. MORIN" <yann.morin.1998@free.fr> writes:
[--SNIP--]
> > Also, I suspect the following patch does not belong to the series; I
> > don't see how it is related to mesa3d or the bump thereof:
> > * board/qemu: add post-build script to aarch64_virt_defconfig
> You need to be logged into a framebuffer console to start weston to be
> able to test the virtio-vulkan GPU.
But qemu_aarch64_virt_defconfig does not even enable mesa3d, so the
rationale does not stsand.
However, a runtime test would indeed be very welcome, but they do not
use the defconfigs; see support/testing/ for examples.
[--SNIP--]
> >> > 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?
AH, OK, then state so in the commit log (e.g.: upstream does not provide
a sh512 in their announcement, just a sha256, so use only that).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-22 20:02 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
2024-08-22 17:24 ` Yann E. MORIN
2024-08-22 19:41 ` Alex Bennée
2024-08-22 20:02 ` Yann E. MORIN [this message]
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=ZseZOEB4XJ0a93P-@landeda \
--to=yann.morin.1998@free.fr \
--cc=alex.bennee@linaro.org \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.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