Github messages for voidlinux
 help / color / mirror / Atom feed
From: atweiden <atweiden@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: Wed, 15 Feb 2023 00:04:10 +0100	[thread overview]
Message-ID: <20230214230410.FF7pwqbsBjMvpBpKlUlmdNFaaQlVvs5UGNMSkGtgRX8@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: 1104 bytes --]

New comment by atweiden on void-packages repository

https://github.com/void-linux/void-packages/pull/41062#issuecomment-1430508155

Comment:
@CameronNemo and anyone else with a pbp running Void,

Have you seen [SvenKiljan/archlinuxarm-pbp](https://github.com/SvenKiljan/archlinuxarm-pbp)? The motivation behind the project seems relevant:

> Manjaro ARM is the semi-official distribution of the Pinebook Pro. The device ships with it, and it seems most development for this particular device ends up in this distribution. The additional Arch Linux ARM packages to support the Pinebook Pro are mostly based on those offered by Manjaro ARM, with some minor adjustments to make them fit better in the Arch Linux ARM ecosystem.

I’ve done some spelunking through pbp-related code in Manjaro and postmarketOS, and it seems to me Void’s current pbp support is already an approximation of the pbp-related code in the aforementioned projects. In any case, the packages at [SvenKiljan/archlinuxarm-pbp-packages](https://github.com/SvenKiljan/archlinuxarm-pbp-packages) look slightly better maintained.

  parent reply	other threads:[~2023-02-14 23:04 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 [this message]
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
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=20230214230410.FF7pwqbsBjMvpBpKlUlmdNFaaQlVvs5UGNMSkGtgRX8@z \
    --to=atweiden@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).