Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure packages built runs flash-kernel #32

Merged
merged 1 commit into from
Feb 22, 2022
Merged

Ensure packages built runs flash-kernel #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 7 additions & 7 deletions .github/workflows/rpi4-kernel-build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# This is a workflow for the RPI4 RT kernel build. It is based on the Dockerfile located in the repo
# Workflow can be started
# Workflow can be started
# - manually
# - after modification of the kernel config fragment file ('.config-fragment')
# - after modification of the kernel config fragment file ('.config-fragment')
# The build takes 1.5 hours and artifacts are available under workflow
# - kernel .deb packages
# TODO:
# TODO:
# - use Dockerfile instead
# - add input parameters
# - create Docker image and push it to the packages
Expand Down Expand Up @@ -118,15 +118,15 @@ jobs:
- name: Get the nearest RT patch to the kernel SUBLEVEL
run: |
cd $HOME/linux_build
cd `ls -d */`
cd `ls -d */`
if test -z $RT_PATCH; then $GITHUB_WORKSPACE/getpatch.sh `make kernelversion | cut -d '.' -f 3` > $HOME/rt_patch; else echo $RT_PATCH > $HOME/rt_patch; fi

- name: Download and unzip RT patch, the closest to the RPI kernel version
run: |
cd $HOME/linux_build
wget http://cdn.kernel.org/pub/linux/kernel/projects/rt/5.4/older/patch-`cat $HOME/rt_patch`.patch.gz \
&& gunzip patch-`cat $HOME/rt_patch`.patch.gz

- name: Patch raspi kernel, do not fail if some patches are skipped
run: |
cd $HOME/linux_build
Expand Down Expand Up @@ -158,10 +158,10 @@ jobs:
run: |
cd $HOME/linux_build
cd `ls -d */` \
&& make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j `nproc` deb-pkg
&& make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- LOCALVERSION=-raspi -j `nproc` deb-pkg

- uses: actions/upload-artifact@v2
with:
name: 'RPI4 RT Kernel deb packages'
path: ~/linux_build/*.deb

16 changes: 0 additions & 16 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,22 +153,6 @@ Assumed you have already copied all ```*.deb``` kernel packages to your ```$HOME
```bash
cd $HOME
sudo dpkg -i *.deb
```

## Adjust ```vmlinuz``` and ```initrd.img``` links

There is an extra step in compare to the x86_64 install because ```update-initramfs``` ignores new kernel

```bash
sudo ln -s -f /boot/vmlinuz-5.4.101-rt53 /boot/vmlinuz
sudo ln -s -f /boot/vmlinuz-5.4.0-1034-raspi /boot/vmlinuz.old
sudo ln -s -f /boot/initrd.img-5.4.101-rt53 /boot/initrd.img
sudo ln -s -f /boot/initrd.img-5.4.0-1034-raspi /boot/initrd.img.old
cd /boot
sudo cp vmlinuz firmware/vmlinuz
sudo cp vmlinuz firmware/vmlinuz.bak
sudo cp initrd.img firmware/initrd.img
sudo cp initrd.img firmware/initrd.img.bak

sudo reboot
```
Expand Down