summaryrefslogtreecommitdiff
path: root/kernels/linux-libre-aarch64
AgeCommit message (Collapse)Author
2020-05-26kernels: remove linux-libre-aarch64Denis 'GNUtoo' Carikli
This kernel has been replaced by linux-libre-64 in libre in an attempt to unify all 64bit kernels made for 32bit rootfs. This has been tested on a SBC that has good upstream support in linux and in u-boot, and a 64bit CPU. That SBC is however not officially supported by Parabola as it still require nonfree binaries in u-boot to boot. The way to go to add official 64bit support ARM computers with 64bit CPUs is to get devices that can at least boot with fully free software. Some SBCs with an Allwinner SOCs like the A64 seem a good target to do that as some SBCs have good support in upstream Linux and u-boot and can boot with free software, and we already have an uboot4extlinux package for many boards with Allwinner SOCs, so we could probably reuse most of that work. However I don't have an SBC like that yet, so until now I tested on a board I was given at a conference. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-01-24linux-libre-aarch64: Enable using a 32bit userspaceDenis 'GNUtoo' Carikli
This is done by enabling CONFIG_COMPAT. Though when importing the configuration on Linux v5.4.8 and enabling this configuration with: make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- xconfig it updated other parts of the the .config as well. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-01-24linux-libre-aarch64: use Image to fix "Bad Linux ARM64 Image magic!"Denis 'GNUtoo' Carikli
Without that patch, /boot/vmlinuz-linux-libre-aarch64 ends up being an Image.gz, however some u-boot configuration and/or versions seem to not like that and fail with the following message: Bad Linux ARM64 Image magic! Making sure that vmlinuz-linux-libre-aarch64 is an Image results in the board booting. However it then fails with: Failed to execute /init (error -8) This might be because the board I used for testing doesn't support runing 32bit binaries and/or because we need to enable more configuration in the kernel to enable that. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-01-21linux-libre-aarch64: various fixes and reduce the diff with linux-libreDenis 'GNUtoo' Carikli
The chromebook package has also been disabled due to the following error: | ==> Starting package_linux-libre-aarch64-chromebook()... | FATAL ERROR: Couldn't open "arch/arm/boot/zImage": No such file or directory | mkimage: Can't read kernel.itb.tmp: Invalid argument | ==> ERROR: A failure occurred in package_linux-libre-aarch64-chromebook(). | Aborting... It could be fixed later on if there is some interest. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-01-21linux-libre-aarch64: Add forgetten config.aarch64 in sourceDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-01-15linux-libre-aarch64: use gcc-initial for nowDenis 'GNUtoo' Carikli
- Compiling a toolchain takes time. - We also need to make sure to get the toolchain right, usually it requires 3 steps (gcc-initial, gcc-intermediate, gcc-final) and here we're trying to do it in two to save compilation time. - The 2 step toolchain worked for newlib but we don't know PKGBUILD examples that do that for glibc based toolchains. - We don't need a libc to build Linux. Because of all that, we depends on the aarch64 gcc-initial toolchain for building it now. Once we have pushed aarch64 gcc, we will need to add it again as a dependency for building this pacakge, in order to be able to build this package and aarch64 userspace applications as well with the same compiler. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-01-09linux-libre-aarch64: Move it in the correct directoryDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>