From: Vagrant Cascadian <vagrant@debian.org>
To: phodina@protonmail.com
Cc: 51775@debbugs.gnu.org, janneke@gnu.org
Subject: [bug#51775] Rebased wip-pinebook-pro branch
Date: Thu, 11 Nov 2021 21:30:09 -0800 [thread overview]
Message-ID: <874k8ic55q.fsf@ponder> (raw)
In-Reply-To: <bOGpoTUJVqKP3U95E5b3BWzge1uPCA2M7df8JZR5Pe3JIxf060qsd3GmdZHGx7KLrk7NmSkvTIH_iFdpfUOgUfObqgHxBATE-niaCGxGaMw=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On 2021-11-11, phodina@protonmail.com wrote:
> Thanks for the amazing work on Pinebook Pro!
>
> Here are the patches rebased on linux-libre-5.10 on Guix master.
...
> Should I also rebase the changes from there?
I stopped working on the wip-pinebook-pro branch in May 2021:
Pinebook Pro no longer WIP
https://lists.gnu.org/archive/html/guix-devel/2021-05/msg00032.html
All the features that seemed important were merged into guix's master
branch at that time, with only very small and minor patches to
linux-libre. I've since tested several other features, such as
NVMe. Some of the quirks seem to have gotten less bad over time, as
support has improved upstream.
I'm not sure it's worth adding a large patchset to support a 5.10.x
linux-libre kernel at this point... What features are missing from the
default kernel?
What guix master branch does lack is decent documentation for the
pinebook-pro; there is a system image configuration but I have not tried
it out so cannot speak to how well it works.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-11-12 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 21:02 [bug#51775] Rebased wip-pinebook-pro branch phodina via Guix-patches via
2021-11-12 5:30 ` Vagrant Cascadian [this message]
2021-11-16 19:20 ` Efraim Flashner
2021-11-16 23:22 ` Vagrant Cascadian
2021-11-17 10:38 ` phodina via Guix-patches via
2021-11-17 16:53 ` Vagrant Cascadian
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=874k8ic55q.fsf@ponder \
--to=vagrant@debian.org \
--cc=51775@debbugs.gnu.org \
--cc=janneke@gnu.org \
--cc=phodina@protonmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.