Need help with kernel source

might be worth setting up a MerSDK somewhere and compiling the kernel with sb2.

This is roughly what we do for device ports, so the same process should be ok

also, if you feel like documenting your process, there's a convenient location it can be put which is currently rather empty https://wiki.merproject.org/wiki/Compiling_Jolla_kernel

@V10lator: Reading the error message might help too ;)

No space left on device?? Hmm, what could be wrong?

Also you could just compile the source normally (only the wlan is out of tree and as you want to replace that one you will have to figure out that bit anyway)

For a pc with an arm cross-compiler installed (assumming it is arm-linux-gcc, naming varies)

# make ARCH=arm CROSS_COMPILE=arm-linux-  sbj_defconfig
# make ARCH=arm CROSS_COMPILE=arm-linux- zImage

(you can add -jX, with X as many threads as you would like to be there to compile the kernel, usually a sane value for X == number of cpus)

And this should generate a working boot.img you can flash with fastboot if the device is unlocked

#!/bin/sh

set -e

BOOTIMG=boot.img
RAMDISKFILE=ramdisk-sailfish.img

# Create ramdisk
echo "Creating dummy ramdisk.."
touch $RAMDISKFILE
gzip -f $RAMDISKFILE

echo "Creating $BOOTIMG.."

KERNEL=arch/arm/boot/zImage

mkbootimg --kernel $KERNEL --ramdisk ${RAMDISKFILE}.gz --cmdline "init=/sbin/preinit root=/dev/mmcblk0p28 rootfstype=btrfs noinitrd androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 maxcpus=2 ip=192.168.2.15::192.168.2.14:255.255.255.0::rndis0:off zcache" --base 0x80200000 --offset 0x02000000 --pagesize 2048 -o $BOOTIMG

echo "Cleaning up.."
rm $RAMDISKFILE*

exit 0

Never mind, the kernel sources where already builded, so removing everything from BUILDROOT and copying the sources out of BUILD seems to have done the trick. For testing I compiled, packaged and published a exfat kernel module: https://openrepos.net/content/v10lator/exfat-nofuse :)

For now I'll just compile modules (well, for compiling modules the full kernel had to be compiled, in fact I have arch/arm/boot/zImage) as I don't feel like touching the kernel right now (not as long as there are open questions like "why is my kernel a zImage when spec file says it has to be uImage?" or "what happens to my Jolla Smartphone after flashing a bad kernel?").

//EDIT: @Philippe De Swert Another question: How to build the kernel on the device when the only thing consuming space on the device is the kernel build and that takes to much space? ;P

@V10lator: Never tried to build it on the phone, always been cross-compiling on a machine that is much faster.