From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/flutter-pi: enable vulkan if possible
Date: Mon, 5 Feb 2024 22:28:36 +0100 [thread overview]
Message-ID: <20240205222836.3b363b8c@windsurf> (raw)
In-Reply-To: <20240121205718.155549-1-adam.duskett@amarulasolutions.com>
Hello Adam,
On Sun, 21 Jan 2024 13:57:18 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> Enable the flutter-pi vulkan option if a suitable driver is enabled.
> Currently, only Mesa provides Vulkan drivers. As such, gating the feature
> behind the BR2_PACKAGE_MESA3D_VULKAN_DRIVER option is reasonable at the moment
> and is done by three other packages already:
> flutter-engine, ivi-home screen, and wlroots.
>
> Furthermore, a dependency on BR2_PACKAGE_VULKAN_LOADER is needed as the
> vulkan-loader package provides the vulkan.pc file, which the configure step
> relies upon.
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
> package/flutter-pi/flutter-pi.mk | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Applied to master, thanks. Of course, at some point it would be nice to
a vulkan virtual package, but let's do that when we have two supported
Vulkan implementations.
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:[~2024-02-05 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 20:57 [Buildroot] [PATCH 1/1] package/flutter-pi: enable vulkan if possible Adam Duskett
2024-02-05 21:28 ` 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=20240205222836.3b363b8c@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox