From: Vagrant Cascadian <vagrant@debian.org>
To: phodina <phodina@protonmail.com>
Cc: 51775@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>,
janneke@gnu.org
Subject: [bug#51775] Rebased wip-pinebook-pro branch
Date: Wed, 17 Nov 2021 08:53:25 -0800 [thread overview]
Message-ID: <87ilwq9116.fsf@ponder> (raw)
In-Reply-To: <ebtdae8w7C8V3JlhiSwMsenmkHojSGhFpkM0MhU-PtligCTVgy0-Dvza7V7j1kqE263UX_27Mfw79FcqjfEEFi9gVha4snMYECxmu2F9Rq4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
On 2021-11-17, phodina@protonmail.com wrote:
> On Wednesday, November 17th, 2021 at 12:22 AM, Vagrant Cascadian <vagrant@debian.org> wrote:
>> On 2021-11-16, Efraim Flashner wrote:
>> > On Thu, Nov 11, 2021 at 09:30:09PM -0800, Vagrant Cascadian wrote:
>> > > 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.
>
> I've used the system image configuration the build image for my Pinebook Pro.
>
> It works, though I experience issue when I reboot the system the
> output on the screen is just some garbage. It has to be turned off
> completely. Then after cold boot it displays everything properly.
>
> So I started to investigate which patch I'm missing and found this
> wip-pinebook-pro branch.
I also experienced that behavior using wip-pinebook-pro back in the
day... so I don't think you'll find a solution there.
> So the way forward would be to check with mainline which patches are
> already accepted, right?
>
> Also I agree it makes no sense to support 5.10 version of the kernel.
Sure, though I don't see any newer branches on:
https://gitlab.manjaro.org/tsys/linux-pinebook-pro
Which is where the patches on wip-pinebook-pro came from...
So my guess is there hasn't been much activity unless someone else is
doing the upstreaming work.
live well,
vagrant
p.s. no need to encrypt messages to me when also sending the same
messages to the public bug tracker! :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2021-11-17 16:57 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
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 [this message]
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=87ilwq9116.fsf@ponder \
--to=vagrant@debian.org \
--cc=51775@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--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.