19:07 <rapha> hi all!

19:11 <rapha> could somebody help me understand the status of mainline support for older CPUs? i own several odroid c1+ and c0 (they're both S805s) and would love to use some newer drivers with them ... no GPU or even HDMI support needed though, not even audio. your wiki says that experimentally-minded end users are welcome ... here is one! :)

19:12 <rapha> also, when you try to follow the how-to in the wiki, you're supposed to first download the recent cross-toolchain from https://releases.linaro.org/components/toolchain/binaries/latest/arm-linux-gnueabihf/ ... unfortunately that URL is 404 :(

19:24 <xdarklight> rapha: Audio support for select boards will come with Linux 5.15. we do have GPU support but HDMI (along with HDMI audio) is still work-in-progress

19:24 <xdarklight> rapha: the main issue (that I am aware of) is that USB hotplug does not work / some USB devices are not recognized

19:24 <rapha> ah, that is interesting, xdarklight

19:24 <rapha> i would need this driver here: https://github.com/EntropicEffect/rtl8822bu ... no hotplug required though. do you think it might work?

19:26 <xdarklight> rapha: I am not sure about these out-of-tree Realtek drivers. there's the rtw88 driver which comes with the mainline kernel but it doesn't have USB support yet. people from https://github.com/ulli-kroll/rtw88-usb are working on USB support, but I am not sure about their upstream plans

19:27 <rapha> hmm, would have to try then, i guess. i don't think the adapter i have (Archer T4U, version 3.20) works with anything else at the moment

19:27 <xdarklight> rapha: as for the linaro toolchain - I use the latest (and greatest!) arm-none-eabi-gcc from the Arch Linux repositories and it's been working fine ever since. I never tried the linaro toolchain

19:27 <rapha> is it feasible to compile the kernel on-device? or does it _have_ to be cross-compiled?

19:28 <rapha> ah, okay ... i do have manjaro on the laptop

19:29 <xdarklight> compiler instructions are the same except: s/arm-linux-gnueabihf-/arm-none-eabi-/

19:43 <rapha> xdarklight: hmm, the feature support table lists eMMC support on S805 as "partial" ... what does that mean? :)

19:43 <xdarklight> rapha: I'll update that. it should say that we have partial SDIO support

19:44 <rapha> oh okay

19:44 <xdarklight> rapha: also for eMMC support we've been missing this config option: https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git/commit/?h=v5.15/configs&id=c8cec81305463d042d51af946b6b273d8367626e - it'll be turned on by default with 5.15. on earlier kernels you manually need to enable it

19:45 <rapha> oh wait, so i should NOT use https://github.com/carlocaione/linux-meson but _actually_ clone from kernel.org?

19:45 <xdarklight> yes, please clone from kernel.org directly

19:45 <rapha> oooh

19:45 <rapha> cool

19:45 <rapha> in that case no reason not to go for 5.15

19:47 <rapha> and what about uboot? can it just remain the way it is for now? as in, first get the new kernel working, then try to get mainline uboot working? or do they only go together?

19:47 <xdarklight> 5.15 is linux-next currently (mainline is at 5.14-rcX). my thinking is: everything has bugs, so if linux-next has something that I'm interested in then I use it ;)

19:47 <xdarklight> there's no mainline u-boot for these older SoCs currently

19:50 <rapha> okay

19:50 <rapha> well, makes it easier for now

19:52 <rapha> hmm wait ... git.kernel.org is quite confusing. i want https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/, right?

19:54 <rapha> wow, that clone is still going on. i do hope it's the right repo :)

19:54 <rapha> time to make some food then

19:55 <xdarklight> yep, that's the correct repo

19:55 <rapha> cool thx!

20:15 <rapha> xdarklight: out of curiosity, what's with the dash after arm-non-eabi?

20:21 <xdarklight> rapha: the whole CROSS_COMPILE is used as a prefix. so for example: instead of invoking gcc the kernel build system needs to invoke arm-non-eabi-gcc. same story with other tools which use this prefix

20:22 <xdarklight> rapha: so the code for invoking gcc is something like: concatenate CROSS_COMPILE with gcc. when you're not cross compiling (say for your x86_64 system) then CROSS_COMPILE will be empty and gcc is used directly

21:05 <rapha> oh okay, that's neat then

21:18 <rapha> it finished building

21:19 <rapha> sooo if i'm feeling adventurous, i'll just replace the old uImage with the new one, reboot, and see what'll happen?

21:20 <rapha> got no UART here right now anyways...

21:22 <rapha> also, not sure about the meson8b-mxq.dtb from the wiki howto ... there's a /boot/dtbs/meson8b_odroidc.dtb which sounds more appropriate

21:23 <rapha> ah, wait, the kernel build produced a meson8b-odroidc1.dtb, that sounds even _more_ appropriate

21:28 <rapha> and also the hex addresses to the bootm command don't match

21:28 <rapha> your howto has three

21:28 <rapha> my boot.ini has a range

21:28 <rapha> hmm, that range covers your three though

21:29 <rapha> maybe you have three because you have that cpio file, too, which i don't have

21:29 <rapha> and then maybe my range is not a range at all, but it says "address, nothing, anotheraddress"

21:29 <rapha> and no fatload for me, but ext4load

21:29 <rapha> it just seems that the alarm ppl set things up differently

21:30 <rapha> hmm, can't learn anything without making mistakes, and tomorrow i'll go fetch the UART anyways. here goes nothing.

21:39 <rapha> hmm, okay, didn't work :P

21:40 <rapha> see you once I find that UART, xdarklight :)