From: moabeat-berlin <moabeat-berlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland)
Date: Sat, 23 Sep 2023 21:03:08 +0200 [thread overview]
Message-ID: <20230923190308.O9SCfVue3U5Aj6TcpTqN7BrqqLFRwr_DUrze2xJ5zjE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46152@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]
New comment by moabeat-berlin on void-packages repository
https://github.com/void-linux/void-packages/pull/46152#issuecomment-1732388822
Comment:
I think I might have a potential solution for this. With a lot of tracing, I was able to make `make prepare` work in `/usr/src/rpi-kernel-headers-6.1.54_1`. Some more missing files had to be added from the kernel sources. In particular these ones:
```
./Kbuild
./kernel/time/timeconst.bc
./kernel/bounds.s
./lib/vdso/Makefile
./lib/vdso/gettimeofday.c
./arch/x86/entry/syscalls/syscall_32.tbl
```
The infinite loop was fixed by adding `Kbuild` in the kernel root. Then some other errors showed up. Also the package `bc` is now required to for `make prepare`.
An accordingly modified `template` for `rpi-kernel` can be found in my repo here: https://github.com/moabeat-berlin/void-packages/blob/rpi-kernel-test/srcpkgs/rpi-kernel/template
After building and installing the packages, dkms works fine:
```
$ sudo xbps-install -R repo/rpi-kernel-test -f rpi-kernel rpi-kernel-headers
Name Action Version New version Download size
rpi-kernel reinstall 6.1.54_1 6.1.54_1 -
rpi-kernel-headers reinstall 6.1.54_1 6.1.54_1 -
Size required on disk: 76MB
Space available on disk: 23GB
Do you want to continue? [Y/n]
[*] Verifying package integrity
rpi-kernel-6.1.54_1: verifying SHA256 hash...
rpi-kernel-headers-6.1.54_1: verifying SHA256 hash...
[*] Collecting package files
rpi-kernel-6.1.54_1: collecting files...
rpi-kernel-headers-6.1.54_1: collecting files...
[*] Unpacking packages
rpi-kernel-6.1.54_1: unpacking ...
rpi-kernel-headers-6.1.54_1: unpacking ...
[*] Configuring unpacked packages
rpi-kernel-6.1.54_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: zfs-2.1.12.
Building DKMS module: zfs-2.1.12... done.
Installing DKMS module: zfs-2.1.12... done.
rpi-kernel-6.1.54_1: installed successfully.
rpi-kernel-headers-6.1.54_1: configuring ...
rpi-kernel-headers-6.1.54_1: installed successfully.
0 downloaded, 2 installed, 0 updated, 2 configured, 0 removed.
```
I'm not sure if my approach is correct. I also checked how other's distribution packages are handling that. In the Raspberry Pi OS Debian package, the binaries are already included. Instead of adding multiple different files scattered across the kernel sources, that would be maybe the better approach. However, I didn't find out yet how you can also cross-compile them to deliver them in the package.
next prev parent reply other threads:[~2023-09-23 19:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:34 [PR PATCH] rpi-kernel: update to 6.1.54 classabbyamp
2023-09-20 12:35 ` rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland) r-ricci
2023-09-20 13:36 ` tsjk
2023-09-20 13:37 ` tsjk
2023-09-20 16:41 ` classabbyamp
2023-09-23 19:03 ` moabeat-berlin [this message]
2023-09-23 19:12 ` classabbyamp
2023-09-23 19:28 ` moabeat-berlin
2023-09-23 19:29 ` moabeat-berlin
2023-09-23 23:11 ` [PR PATCH] [Updated] " classabbyamp
2023-09-23 23:12 ` classabbyamp
2023-09-23 23:13 ` classabbyamp
2023-09-23 23:15 ` classabbyamp
2023-09-23 23:28 ` moabeat-berlin
2023-09-23 23:29 ` moabeat-berlin
2023-09-23 23:59 ` classabbyamp
2023-09-24 0:20 ` moabeat-berlin
2023-09-24 0:21 ` moabeat-berlin
2023-09-24 17:53 ` tsjk
2023-09-24 17:54 ` tsjk
2023-09-24 17:54 ` tsjk
2023-09-24 19:53 ` tsjk
2023-09-25 6:33 ` [PR PATCH] [Updated] " classabbyamp
2023-09-25 6:40 ` classabbyamp
2023-09-25 8:44 ` tsjk
2023-09-25 8:45 ` tsjk
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:37 ` tsjk
2023-09-29 18:40 ` classabbyamp
2023-09-29 18:41 ` tsjk
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:05 ` classabbyamp
2023-09-29 19:37 ` [PR PATCH] [Updated] " classabbyamp
2023-09-29 20:57 ` moabeat-berlin
2023-09-29 21:09 ` classabbyamp
2023-09-29 21:18 ` classabbyamp
2023-09-29 21:24 ` [PR PATCH] [Updated] " classabbyamp
2023-09-29 22:01 ` rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland, rpi-eeprom) classabbyamp
2023-09-30 2:41 ` [PR PATCH] [Merged]: " classabbyamp
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=20230923190308.O9SCfVue3U5Aj6TcpTqN7BrqqLFRwr_DUrze2xJ5zjE@z \
--to=moabeat-berlin@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).