From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mesa: add Broadcom vulkan driver
Date: Wed, 05 Jan 2022 08:40:46 +0100 [thread overview]
Message-ID: <20220105074046.VqHVNuSs9DelbW0H4eHkjVC2hVqwzzGNym7XCt_Cfj4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34778@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
There's a merged pull request on the void-packages repository
mesa: add Broadcom vulkan driver
https://github.com/void-linux/void-packages/pull/34778
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, aarch64
---
I created a new subpackage to build vulkan drivers for the Raspberry Pi 4. They seem to be working correctly, given the output of `vulkaninfo` from `Vulkan-Tools`, but I haven't actually tested any graphical workload, since `vkcube` is missing from `Vulkan-Tools` in `aarch64`.
P.S. -- I removed the update to 21.3.3 to keep this PR more feature isolated.
prev parent reply other threads:[~2022-01-05 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 2:47 [PR PATCH] mesa: update to 21.3.3 and " sug0
2022-01-02 1:29 ` [PR PATCH] [Updated] " sug0
2022-01-02 1:37 ` [PR PATCH] [Closed]: " sug0
2022-01-02 1:37 ` [PR PATCH] [Updated] " sug0
2022-01-03 21:54 ` mesa: " ericonr
2022-01-03 22:24 ` sug0
2022-01-03 22:24 ` [PR PATCH] [Updated] " sug0
2022-01-03 22:24 ` sug0
2022-01-03 22:27 ` sug0
2022-01-03 22:35 ` [PR PATCH] [Updated] " sug0
2022-01-04 8:00 ` ericonr
2022-01-04 12:41 ` q66
2022-01-04 15:39 ` [PR PATCH] [Updated] " sug0
2022-01-04 15:40 ` sug0
2022-01-04 16:24 ` q66
2022-01-05 7:40 ` ericonr [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=20220105074046.VqHVNuSs9DelbW0H4eHkjVC2hVqwzzGNym7XCt_Cfj4@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).