From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: pinebookpro-firmware: update to 0.0.20220515, fix dead links.
Date: Sun, 09 Jun 2024 06:37:36 +0200 [thread overview]
Message-ID: <20240609043737.28E0F2B24A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49200@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
There's a closed pull request on the void-packages repository
pinebookpro-firmware: update to 0.0.20220515, fix dead links.
https://github.com/void-linux/void-packages/pull/49200
Description:
This is firmware for broadcom 43456
It's unclear if this firmware is needed at all.
linux-firmware has broadcom 43455 with patchset for pinebookpro
Manajro has license as "unknown".
The linux-firmware mailing suggests that the firmware hasn't been upstreamed due to licensing issues:
https://lore.kernel.org/linux-firmware/CAMEGJJ2XYvGEekfLzjL1KE6VUF-71s+S8RbJ1DuBkYU98F9nsg@mail.gmail.com/
Should void be distributing this at all?
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2024-06-09 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 4:35 [PR PATCH] " Calandracas606
2024-03-09 4:36 ` [PR PATCH] [Updated] " Calandracas606
2024-06-08 1:47 ` github-actions
2024-06-09 4:37 ` Calandracas606 [this message]
2024-06-09 4:37 ` Calandracas606
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=20240609043737.28E0F2B24A@inbox.vuxu.org \
--to=calandracas606@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).