From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Replace pbp kernel package with linux package
Date: Tue, 10 Oct 2023 20:35:31 +0200 [thread overview]
Message-ID: <20231010183531.09rMxuGub1uGIRyEtfyhC8poAJTbJiGVqA49rKhUiQ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46563@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
New comment by Calandracas606 on void-packages repository
https://github.com/void-linux/void-packages/pull/46563#issuecomment-1756008296
Comment:
> > Any changes needed on the image creation side of things? In principal, no opposition.
>
> Yes, will do this on the weekend. Not sure if we even want to keep the creation of a pbp specific image. A generic aarch64 efi image should boot just fine (which is still missing on mklive), and we could just suggest users to have a uboot (or towboot) on their SPI.
Agreed.
TowBoot's sentiment is that [the distribution shouldn't be managing the firmware used to boot the system.](https://tow-boot.org/FAQ.html)
Additionally, I believe that the u-boot image that we distribute isn't ideal, and has some problems with "suspend to ram" (or rockchip's fake suspend to ram). I haven't completely pinned that issue down to our u-boot image, but it was resolved when I switched to [megi's u-boot images and rk2aw bootloader](https://xnux.eu/rk2aw/).
Ultimately, I am of the opinion that it should be up to the user to install and manage their own boot-loader.
Having a generic aarch64 image is likely best, generating an appropriate extlinux
I have a successfully running pbp musl, using rk2aw in SPI, megi's uboot on emmc, generic base-system, linux, u-boot-menu + pinebookpro-firmware. In the past, I've had success booting with Towboot -> grub -> EFI
next prev parent reply other threads:[~2023-10-10 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 17:06 [PR PATCH] " Johnnynator
2023-10-10 17:14 ` [PR PATCH] [Updated] " Johnnynator
2023-10-10 17:39 ` Johnnynator
2023-10-10 17:48 ` CameronNemo
2023-10-10 17:51 ` CameronNemo
2023-10-10 18:10 ` Johnnynator
2023-10-10 18:11 ` Calandracas606
2023-10-10 18:23 ` [PR PATCH] [Updated] " Johnnynator
2023-10-10 18:24 ` Johnnynator
2023-10-10 18:35 ` Calandracas606 [this message]
2024-01-09 1:47 ` github-actions
2024-04-09 1:45 ` github-actions
2024-04-23 1:45 ` [PR PATCH] [Closed]: " github-actions
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=20231010183531.09rMxuGub1uGIRyEtfyhC8poAJTbJiGVqA49rKhUiQ4@z \
--to=calandracas606@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).