Hello  Illegalum,wfk,
I created 3 instalable packages with a '4.14.165' kernel from hardkernel repo..
to install it you can follow bellow intructions,

It would be nice to know if it boots, and if ethernet is working correctly,
The idea is creating a image for hc1, with zram as swap using lz4 algo on it

but we need first a stable kernel..
in the share folder bellow is also a 'log' file, with the compilation log process..

if this works nicelly, I will tune the kernel for big.LITTLE on hc1 cpu

Hi Illegalum,
Ok, no problem, no rush

Hi wfk,
For the work Illegalum have done, he experienced problems with the network card, I believe?!( using the devuan image for xu4.. )

I found there are indeed a dts in mainline for hc1..
I compiled 5.5.7 kernel, and I were checking it with Illegalum..

My Kernel gave a kernel panic( I also saw a compiler warning about a pointer not been initialized first.. in compilation process)..
But it could also be that my toolchain is the one to blame..

I am with Linaro 7.5 unfortunately, since ARM only provides amd64 cross toolchains...
So I am locked on 7.5 cross toolchains..

What kernel are you using?

Best Regards,
tux

Hello Illegalum,
thanks,

I took a loot at boot.ini, and adapted it for a mainline kernel 5.5.7, and to Odroid hc1 dtb.
I created a share with the kernel and the boot.ini new files..
This share here, contains the deb packages to try a mainline kernel, and also the new boot.ini file..

Backup first your boot.ini file:
cp boot.ini boot.ini.backup

Then copy to the sdcard, the contents of the shared folder:
linux-headers-5.5.7_5.5.7-1_armhf.deb,
linux-image-5.5.7_5.5.7-1_armhf.deb,
linux-libc-dev_5.5.7-1_armhf.deb

Copy also 'boot.ini.new' to /boot,

then boot the board, install the new kernel:
dpkg -i *.deb
change 'boot.ini.new' to 'boot.ini':
mv /boot/boot.ini.new /boot/boot.ini

then restart and check if that kernel, works well in your board, if it doesn't:
dpkg -l |grep -E "linux-.*(image|headers|libc-dev)"

See the 5.5.7 installed packages and remove them:
apt-get remove --purge linux-headers-5.5.7 linux-image-5.5.7 linux-libc-dev
get back your 'boot.ini' file:
mv /boot/boot.ini.backup /boot/boot.ini

And restart..

It would be nice to get some feedback from you, since you own one of this boards

Best Regards,

hello, yes it was nice

Can you do this as root ?
find /boot -type f -exec ls -l {} \;

to see how boot loader is configured
I already compiled a kernel

regards,
tux

You came to the right place

At least in kernel 5.5.6, exists a device tree source file for it
/arch/arm/boot/dts/exynos5422-odroidhc1.dts
you can build it if you want to

For hc2, I don't find it

Can you do a dmesg, in the system were everything works?
also a zcat /proc/config.gz ?

Thanks,
could be that I make a build for it, but not yet, some day..

To build it, you first need a crosscompiler if you are in another arch..:
you will need a 'arm-linux-gnueabihf' compiler..
if you are in amd64 arch..
apt-get install flex bison make libssl-dev bc quilt rsync fakeroot libncurses-dev

download the crosscompiler,
arm-linux-gnueabihf compiler,
Extract it to the correct place you want, then update your path:
export PATH=$PATH:$PWD/path_to_ToolChain/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin

then :
make -C kernel_path ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-  clean

So now you have your kernel tree clean

So, for hc1...
You have a distro from devuan for Odroid xu4,
https://mirror.leaseweb.com/devuan/devu … xu4.img.xz

In the distro were it is working,
zcat /proc/config.gz

copy that file content to:
'your_kernel_path/.config',
    you can also copy same file to:
        'your_kernel_path/arch/arm/configs/exynos5422-odroidhc1_defconfig'

this will parse and generate your .config file..
make -C kernel_path ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-  exynos5422-odroidhc1_defconfig

Create deb packages to install:
make -C kernel_path ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- deb-pkg -j$(nproc)
several deb packages will be created(deb packages have several things that need to be adjusted, but it will work I believe without that adjustments..)..
You just need to install them on the new system, and adapt names..

or

Generate several directories with Image,dtbs,modules:
make -C kernel_path ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- Image dtbs modules -j$(nproc)

pass everything to new system, update names, don't forget the content of 'boot.scr'.. or boot.cmd , and that's it

This brief explanation for the kernel..
try it, and check if you are able to boot...

Best Regards,
tux

hi uther,
thanks, so they don't use zram as swap, on raspbian
they have a lot of modules that could be interesting to match with something similar in mainline

I am on freenode
some issues with my machine prevented me from 2 days, but I am recovering now

hello therion23,
The idea would be to have mainline kernel running on raspberryPI4..

Initial support landed recently, now in kernel 5.6 comes thermal driver,
I just saw the commits to mainline
create mode 100644 drivers/thermal/broadcom/bcm2711_thermal.c
delete mode 100644 drivers/thermal/cpu_cooling.c
create mode 100644 drivers/thermal/cpufreq_cooling.c
create mode 100644 drivers/thermal/cpuidle_cooling.c
create mode 100644 drivers/thermal/sun8i_thermal.c

yes, also thermal driver for Allwiner H6( but I have a patch for it, in the meantime, and its applied so, no hurry )

Long Story short,
we( me and uther ), have been trying to have a server Image for RPi4, with mainline support, and trying to avoid the blob madness with RaspberryPi firmware/kernel trees..

The Last image is in this NetWork Share:
The Image is 'devuan-ascii-rpi4-arm64-0.2-beta.img.xz'

'Kernel/headers/Libc-dev' deb packages for '5.5.0' is also in the share( in the event of Success, can be copied to sdcard and installed via 'dpkg -i' )..

'/etc/default/rng-tools'
Point automatically to  '/dev/urandom'( just in case.. when we managed to boot it, we will see if a driver exists, we will change to it.. ), in the meantime..
HRNGDEVICE=/dev/urandom

'config.txt'
arm_64bit=1
kernel=bootloader.bin
total_mem=3072

'bootloader.bin':
Is the u-boot that then will load the 'vmlinuz'

'boot.cmd'
The same content as 'boot.scr', but is a text human readable file

'boot.scr'
Is the binary file uboot( 'bootloader.bin' ) will load with all the instructions to start the Linux Kernel for Raspberry Pi4( now..if it just worked would be nice )

'vmlinuz'
Is the Linux Kernel... the name contains a 'z'( vmlinuz ), but the Image is not compressed, so its a 'vmlinux' binary file (  in ARM64 is impossible to boot compressed Kernels, at least for now.. ).
So even tough the name suggests compression its a uncompressed kernel..

-------------------------------------------
The Idea..
config.txt -> bootloader.bin->uboot.scr->vmlinuz init=/sbin/init

The problem,
I don't have a RPi4,
Uther have been doing all the testing( which I am also grateful to him, for helping out on this ).

We tried to reach more colleagues( to increase the probability of Success ), but some say they cannot download the Image, other doesn't stepped in..

For what it seems the Image doesn't boot, it stops in the Rainbow( initially when hdmi is connected to monitor )..
It his needed further testing, getting the Serial uart console data to see what is happening..
Or even changing something, that we were unable to figure out..

If you, can help us out, it would be very nice
We know that the boot process in RPi4 changed, and maybe we are stuck there

hello uther,

when you don't have sdcard inserted it indeed complains about 'arasan-emmc0'..
but I built the driver for it in the last beta..

What is strange to me is that it indeed starts 'start4cd.elf', which is a cut down version of start4.elf..

Which means memory for GPU is low..
On previous rpi's it would work, running the bootloader and it then loading vmlinuz..
By some reason is here doesn't work..

try to encrise 'gpu_mem' in config.txt to 64.
gpu_mem=64

And see if something goes different..
I am still actively trying to find a way to boot it with mainline kernel..

humm,
The idea of a mainline kernel would be very nice, but it seems we need something more..

And if you change in 'config.txt'
kernel parameter to:
kernel=vmlinuz

You still get stuck at the rainbow?

Thanks in Advance for your help on this

Nice Job!!

The first link you showed it prints a emmc controller, arasan-emmc0,
I don't know If I included this driver, in Kernel Image..
I will check, and if its not there I will update image!

In the mean time , can you please test image 'devuan-ascii-rpi4-arm64-0.2-beta.img.xz' ?

Any one Interested in provide thoughts about this?

Hello uther,
Thanks a lot for the effort..

If you unplug and plug it again in your computer what is the 'dmesg' output( last information of it )?
try debugging the output of the boot process with the Raspbian image..to test it..
( If you succeed, then try with the new Image 'devuan-ascii-rpi4-arm64-0.2-beta.img.xz' )

And see if you get something..
Maybe the USB device is numbered differently.. I usually get on my device 'ttyUSB0'.

Edit: I forgot,
The RX of Converter is connected to the TX, of the Board
The TX of Converter is connected to the RX of the board