From: phodina via Guix-patches via <guix-patches@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
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 10:38:42 +0000 [thread overview]
Message-ID: <ebtdae8w7C8V3JlhiSwMsenmkHojSGhFpkM0MhU-PtligCTVgy0-Dvza7V7j1kqE263UX_27Mfw79FcqjfEEFi9gVha4snMYECxmu2F9Rq4=@protonmail.com> (raw)
In-Reply-To: <87wnl7u1nc.fsf@ponder>
Hi,
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.
>
> > The pinebook pro boots from the SD card first if it's present, right? I
> >
> > have one sitting next to me, I can take some time and build an image and
> >
> > test it out.
>
> Pretty sure the hard-coded bootrom boot order is SPI -> eMMC -> microSD
>
> -> ... other stuff
>
Yes there is bootrom which launches the u-boot. I've updated mine to latest version and it let's me select, though boots first eMMC.
> So it depends on what else you have installed. I've never installed
>
> u-boot to SPI and yanked the eMMC to keep updates easier to fix when
>
> regressions happen; the u-boot loaded from microSD boots off of NVMe
>
> nicely...
>
> live well,
>
> vagrant
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.
Petr
next prev parent reply other threads:[~2021-11-17 10:39 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 [this message]
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='ebtdae8w7C8V3JlhiSwMsenmkHojSGhFpkM0MhU-PtligCTVgy0-Dvza7V7j1kqE263UX_27Mfw79FcqjfEEFi9gVha4snMYECxmu2F9Rq4=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=51775@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=janneke@gnu.org \
--cc=phodina@protonmail.com \
--cc=vagrant@debian.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.
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.