From: "Alex Bennée" <alex.bennee@linaro.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH v4 5/6] package/vkmark: add vkmark benchmarking tool
Date: Mon, 02 Jun 2025 13:44:44 +0100 [thread overview]
Message-ID: <87seki48jn.fsf@draig.linaro.org> (raw)
In-Reply-To: <6695cdd8cafdf2352d931b4c054f8250@free.fr> (Julien Olivain's message of "Sat, 31 May 2025 23:31:40 +0200")
Julien Olivain <ju.o@free.fr> writes:
> Hi Alex,
>
> Thanks for the patch.
>
> On 03/03/2025 17:15, Alex Bennée wrote:
>> We build from the recent 2025.1 release although we need one commit
>> from master to better handle the missing KHR_display extension.
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> v4
>> - fix tab vs space damage
>> - don't if BR2_PACKAGE_VKMARK_FLAVOR_ANY
>> - make comments properly depend
>> - use the new 2025.01 release
>> - add sha256sum of COPYING-LGPL2.1
>> - alphabetic sort of initial VKMARK_DEPENDENCIES
>> - add vulkan error probing patch
<snip>
>> diff --git
>> a/package/vkmark/0001-display-Properly-handle-Vulkan-errors-during-probing.patch
>> b/package/vkmark/0001-display-Properly-handle-Vulkan-errors-during-probing.patch
>> new file mode 100644
>> index 0000000000..7e2e43a946
>> --- /dev/null
>> +++
>> b/package/vkmark/0001-display-Properly-handle-Vulkan-errors-during-probing.patch
>> @@ -0,0 +1,77 @@
>> +From adf1aa346d99d29ad2c5c945c3e4de5e0e3e12cb Mon Sep 17 00:00:00 2001
>> +From: Alexandros Frantzis <alexandros.frantzis@collabora.com>
>> +Date: Thu, 27 Feb 2025 14:33:49 +0200
>> +Subject: [PATCH] display: Properly handle Vulkan errors during probing
>> +
>> +The vk::createInstance() function throws an exception on error,
>> +so handle it instead of checking for a null return value.
>> +
>> +Signed-of-by: Alex Bennée <alex.bennee@linaro.org>
>
> There is a small typo here. It should be:
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> This is reported by "utils/docker-run make check-package".
>
> package/vkmark/0001-display-Properly-handle-Vulkan-errors-during-probing.patch:0:
> missing Signed-off-by in the header
> (https://nightly.buildroot.org/#_format_and_licensing_of_the_package_patches)
>
> Could you send an updated version of this patch, please?
I think this is now handled upstream by:
https://github.com/vkmark/vkmark/pull/72
So I can switch to building from current HEAD or ask the vkmark people
to cut a new release.
--
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:[~2025-06-02 12:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 16:15 [Buildroot] [PATCH v4 0/6] Add vkmark graphics benchmarking tool Alex Bennée
2025-03-03 16:15 ` [Buildroot] [PATCH v4 1/6] testing: drop unneeded vga/vnc stanzas from QEMU invocation Alex Bennée
2025-05-31 22:40 ` Julien Olivain
2025-06-12 20:04 ` Arnout Vandecappelle via buildroot
2025-03-03 16:15 ` [Buildroot] [PATCH v4 2/6] package/vulkan-sdk: new package Alex Bennée
2025-03-03 16:15 ` [Buildroot] [PATCH v4 3/6] package/vulkan-[headers|loader|tools]: bump to 1.4.307 release Alex Bennée
2025-03-03 16:15 ` [Buildroot] [PATCH v4 4/6] package/vulkan-tools: suppress isystem being passed Alex Bennée
2025-05-31 21:28 ` Julien Olivain
2025-06-03 13:39 ` Alex Bennée
2025-03-03 16:15 ` [Buildroot] [PATCH v4 5/6] package/vkmark: add vkmark benchmarking tool Alex Bennée
2025-05-28 14:00 ` Heiko Thiery
2025-05-29 13:27 ` Heiko Thiery
2025-05-31 21:14 ` Julien Olivain
2025-06-02 8:19 ` Heiko Thiery
2025-05-31 21:31 ` Julien Olivain
2025-06-02 12:44 ` Alex Bennée [this message]
2025-03-03 16:15 ` [Buildroot] [PATCH v4 6/6] support/testing: add test for vkmark package Alex Bennée
2025-05-31 21:51 ` Julien Olivain
2025-06-03 13:40 ` Alex Bennée
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=87seki48jn.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=ju.o@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