From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro: kernel: update to 6.1.9, base: drop firmware dependency, use ALSA UCM
Date: Thu, 16 Feb 2023 06:26:10 +0100 [thread overview]
Message-ID: <20230216052610.cVutAAs8hS-H44u3qTuyzTpUuImDoi9ssMatJZlNnmc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/pull/41062#issuecomment-1432532231
Comment:
So many of those are altmode DP related, which I deliberately do not support because it never worked reliably and required invasive, never going to be upstreamed patches. Others are not PBP related at all. If it says Allwinner for example, that is not targeting the PBP. That first one is also not related to the WiFi chipset used on the PBP.
For any others, submit them upstream if they help you. That way the patch gets more scrutiny and helps every distro, not just us. I am more likely to remove patches than add them at this point in time. I have no interest in trying to keep up with the nightmare that is Manjaro ARM's kernel.
These are the only ones that seem both PBP related and upstream-able:
* [linux-manjaro/2002-brcmfmac-USB-probing-provides-no-board-type.patch](https://github.com/SvenKiljan/archlinuxarm-pbp-packages/raw/main/linux-manjaro/2002-brcmfmac-USB-probing-provides-no-board-type.patch)
* [linux-manjaro/2003-arm64-dts-rockchip-Work-around-daughterboard-issues.patch](https://github.com/SvenKiljan/archlinuxarm-pbp-packages/raw/main/linux-manjaro/2003-arm64-dts-rockchip-Work-around-daughterboard-issues.patch)
* [linux-manjaro/4007-ASoC-codec-es8316-DAC-Soft-Ramp-Rate-is-just-a-2-bit-control.patch](https://github.com/SvenKiljan/archlinuxarm-pbp-packages/raw/main/linux-manjaro/4007-ASoC-codec-es8316-DAC-Soft-Ramp-Rate-is-just-a-2-bit-control.patch)
* [linux-manjaro/4008-arm64-dts-rk3399-pinebook-pro-Fix-codec-frequency-after-boot.patch](https://github.com/SvenKiljan/archlinuxarm-pbp-packages/raw/main/linux-manjaro/4008-arm64-dts-rk3399-pinebook-pro-Fix-codec-frequency-after-boot.patch)
next prev parent reply other threads:[~2023-02-16 5:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 16:12 [PR PATCH] pinebookpro-kernel: update to 6.1.0 CameronNemo
2022-12-21 18:58 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 6.1.1 CameronNemo
2023-02-06 2:29 ` CameronNemo
2023-02-06 2:32 ` pinebookpro: kernel: update to 6.1.1, base: drop firmware dependency, use ALSA UCM CameronNemo
2023-02-06 12:18 ` petersen77
2023-02-06 15:46 ` CameronNemo
2023-02-06 15:48 ` CameronNemo
2023-02-08 21:54 ` pinebookpro: kernel: update to 6.1.9, " petersen77
2023-02-14 20:59 ` [PR PATCH] [Merged]: " paper42
2023-02-14 23:04 ` atweiden
2023-02-15 1:11 ` CameronNemo
2023-02-15 3:18 ` atweiden
2023-02-15 16:29 ` CameronNemo
2023-02-15 16:29 ` CameronNemo
2023-02-16 3:57 ` atweiden
2023-02-16 5:26 ` CameronNemo [this message]
2023-02-16 6:56 ` atweiden
2023-02-16 9:14 ` CameronNemo
2023-02-17 4:25 ` atweiden
2023-02-17 5:30 ` CameronNemo
2023-02-17 5:30 ` CameronNemo
2023-02-17 19:45 ` atweiden
2023-02-17 22:53 ` CameronNemo
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=20230216052610.cVutAAs8hS-H44u3qTuyzTpUuImDoi9ssMatJZlNnmc@z \
--to=cameronnemo@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).