Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New packages: rockpro64-base and rockpro64-uboot
Date: Mon, 25 Jul 2022 04:14:38 +0200	[thread overview]
Message-ID: <20220725021438.ydwH2hlSvRnj7abD8htjjcNgGgPR1VIN8KNmCEmyVuE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33556@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2434 bytes --]

There's a closed pull request on the void-packages repository

New packages: rockpro64-base and rockpro64-uboot
https://github.com/void-linux/void-packages/pull/33556

Description:
#### General
- [X] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl

I have not built the package native on aarch64, only crossbuilds on x86_64 with aarch64 and aarch64-musl. Both built successfully with xbps-src -K.
Most of the work is copied from the pinebook-pro packages, as both are very similar using the RK3399 soc. I did not create a rockpro64 specific kernel as it did not seem necessary. I have tested using kernels 5.10, 5.13 and 5.14. The latter two versions produce fewer errors when booting (loglevel=4).
I don't know if this is relevant but I have also created images with the zfs dkms module. It only succeeded building on kernel version 5.10, however not without errors, zfs does work though.
I have not updated U-Boot to the latest version (2021-10 as of now) because it fails to build. Earlier this week it was fine so I don't yet know what happened. The second to last version (2021-07) is still very recent and does work fine.
The pinebook-pro template creates a boot.scr to boot the image, the rock64 template uses extlinux to boot, after a bit of research I opted to go with extlinux because that is what everyone else is doing (manjaro, ayufan, armbian) and this simplifies the patch for void-mklive to create an image, it does require u-boot-menu as an extra dependency.
Most of the patches come straight from the pinebookpro-uboot package with a few features taken from [Sigmaris's U-Boot](https://github.com/sigmaris/u-boot/). A description of the details can be found in the patch files.


      parent reply	other threads:[~2022-07-25  2:14 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  5:44 [PR PATCH] " tiemenwerkman
2021-10-15 21:53 ` CameronNemo
2021-10-24 13:54 ` tsndqst
2022-03-04  4:59 ` Anachron
2022-03-17  6:55 ` Anachron
2022-03-17  6:55 ` Anachron
2022-03-17  6:56 ` Anachron
2022-03-17  9:14 ` Anachron
2022-03-17  9:18 ` Anachron
2022-03-17  9:52 ` Anachron
2022-03-17 14:58 ` Anachron
2022-03-18 20:23 ` Anachron
2022-03-18 20:24 ` Anachron
2022-03-18 20:52 ` tsndqst
2022-03-18 20:53 ` tsndqst
2022-03-18 21:07 ` Anachron
2022-03-18 22:38 ` tsndqst
2022-03-21 13:09 ` Anachron
2022-03-21 15:34 ` Anachron
2022-03-21 20:02 ` Anachron
2022-03-21 20:15 ` Anachron
2022-03-21 20:26 ` Anachron
2022-03-21 20:34 ` Anachron
2022-03-21 20:42 ` Anachron
2022-03-21 20:43 ` Anachron
2022-03-21 20:46 ` Anachron
2022-03-21 21:01 ` Anachron
2022-03-21 21:04 ` Anachron
2022-03-22  1:17 ` tsndqst
2022-03-22  2:48 ` zen0bit
2022-03-22  6:30 ` Anachron
2022-03-22  6:31 ` Anachron
2022-03-22  7:25 ` Anachron
2022-03-22  7:40 ` Anachron
2022-03-22  7:46 ` Anachron
2022-03-22  9:12 ` Anachron
2022-03-22 20:35 ` CameronNemo
2022-03-22 20:36 ` CameronNemo
2022-03-22 21:02 ` Anachron
2022-03-23 12:22 ` Anachron
2022-03-23 17:25 ` Anachron
2022-03-25 13:00 ` [PR REVIEW] " tsndqst
2022-03-25 20:45 ` CameronNemo
2022-03-25 20:55 ` Anachron
2022-03-25 21:06 ` tsndqst
2022-04-10  5:45 ` Anachron
2022-04-10  5:48 ` Anachron
2022-04-10  5:53 ` Anachron
2022-07-10  2:14 ` github-actions
2022-07-25  2:14 ` github-actions [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=20220725021438.ydwH2hlSvRnj7abD8htjjcNgGgPR1VIN8KNmCEmyVuE@z \
    --to=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).