diff options
author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2020-01-08 19:37:35 +0100 |
---|---|---|
committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2020-01-08 19:47:50 +0100 |
commit | 3d00a8089ed6fd5875be75733adc2da3768ba252 (patch) | |
tree | 5ed74e627f761c0054ae4bbc71185c380f6806f6 /kernels/linux-libre-aarch64/0006-set-default-cubietruck-led-triggers.patch | |
parent | b8dd027e7c1b4103263135b75537d7117792ac8e (diff) | |
download | abslibre-3d00a8089ed6fd5875be75733adc2da3768ba252.tar.gz abslibre-3d00a8089ed6fd5875be75733adc2da3768ba252.tar.bz2 abslibre-3d00a8089ed6fd5875be75733adc2da3768ba252.zip |
kernels: add linux-libre-aarch64
Some System On a Chip (SOC) have 64bit ARM CPUs that are also
capable of running arm 32bit applications.
Since:
- Parabola doesn't have an aarch64 package repository yet
- The devicetree of devices using such System On a Chip
are not compiled when using the armv7 defconfig
- Drivers or other platform support code for such hardware
might also not be compiled in with the armv7 defconfig
- This approach has already been tested with the linux-libre-x86_64
kenrel
It's then a good idea to add support for such devices by adding
an arrch64 kernel as the maintenance and work is minimal.
The downside is that the external kernel modules that are either
compiled against the kernel or using DKMS will not work by default.
It's however still possible to compile them by hand by using
ARCH= and CROSS_COMPILE= as it is done for this kernel, so it
should be relatively easy to add support for the non-dkms modules.
As for DKMS, someone would need to look into it to understand how
to pass it the make flags (ARCH= and CROSS_COMPILE=) that are
required to automatically build modules.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'kernels/linux-libre-aarch64/0006-set-default-cubietruck-led-triggers.patch')
0 files changed, 0 insertions, 0 deletions