From: Vagrant Cascadian <vagrant@debian.org>
To: Vincent Legoll <vincent.legoll@gmail.com>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Pinebook pro TODO
Date: Sat, 24 Apr 2021 09:23:47 -0700 [thread overview]
Message-ID: <87h7jvodm4.fsf@yucca> (raw)
In-Reply-To: <CAEwRq=pAOLJb-GrG6JFAo7sAFoHJf5aCDKktc=w5LynXUfGLSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
On 2021-04-24, Vincent Legoll wrote:
> now that I've got my pbp running guix, I have
> more questions.
>
> The kernel is still "manjaro kernel", should
> this be changed to reflect some changes
> we have made ?
That's probably just tweaking the kernel defconfig a bit more.
> What about the panfrost patch ?
> https://issues.guix.gnu.org/40835
> https://lists.gnu.org/archive/html/guix-patches/2020-04/msg01317.html
The panfrost changes for mesa are in guix since 1.2.0rc1, commit:
ee401ed9249fbe284ef1b9b437d39207ca88131b
I think that bug report addressed multiple other issues, so didn't
exactly seem appropriate to close.
> The wip-pbp branch:
> why does it get merges from master instead
> of being rebased (as wip-* branches can be) ?
It has some history that makes rebasing complicated that I'd rather not
loose for now. When it's ready to merge to master, I'll go through the
trouble to rebase it.
> How can one help getting things going upstream ?
I think the only things left are the 22 kernel patches in the
wip-pinebook-pro branch in
gnu/packages/patches/linux-libre-pinebook-pro-* ... many are flagged as
hacks in the comments and need to be re-implemented in a way that makes
the patches upstreamable... and then submitted upstream.
Might be able to further refactor those patches to get something useable
directly on guix master, but I haven't been comfortable pushing such
large changes to master (~2000 lines of code, ~3000 line kernel
config).
Although the patches are only applied to linux-libre-pinbook-pro and
shouldn't affect other packages at all...
There are also some changes (usb-c alternate display mode, wifi) that
may need to be removed for linux-libre; I believe linux-libre makes it
impossible to load the non-free firmware in practice, but the support
should just not be present at all.
The wip-pinebook-pro patches are stalled at 5.10, but at least 5.10 is a
long-term support kernel series:
https://gitlab.manjaro.org/tsys/linux-pinebook-pro.git
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-04-24 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 9:12 Pinebook pro TODO Vincent Legoll
2021-04-24 16:23 ` Vagrant Cascadian [this message]
2021-04-24 18:41 ` Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7jvodm4.fsf@yucca \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=vincent.legoll@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).