warpme_ has quit [Quit: Connection closed for inactivity]
psydroid has quit [Write error: Connection reset by peer]
Las[m] has quit [Read error: Connection reset by peer]
psydroid has joined #linux-amlogic
Las[m] has joined #linux-amlogic
camus1 has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
camus1 has quit [Ping timeout: 240 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
xdarklight has quit [*.net *.split]
BlueMatt has quit [*.net *.split]
BlueMatt has joined #linux-amlogic
libera- has joined #linux-amlogic
libera- is now known as xdarklight
xdarklight has joined #linux-amlogic
xdarklight has quit [Changing host]
cmeerw has joined #linux-amlogic
cmeerw has quit [Ping timeout: 250 seconds]
chewitt has quit [Quit: Zzz..]
Ballerburg9005 has joined #linux-amlogic
warpme_ has joined #linux-amlogic
Ballerburg9005 has quit [Ping timeout: 245 seconds]
sputnik_ has quit [Ping timeout: 265 seconds]
Ballerburg9005 has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
cmeerw has joined #linux-amlogic
repk has quit [Ping timeout: 250 seconds]
repk has joined #linux-amlogic
rapha has joined #linux-amlogic
<rapha>
hi all!
<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! :)
<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
<xdarklight>
rapha: the main issue (that I am aware of) is that USB hotplug does not work / some USB devices are not recognized
<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
<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
<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
<rapha>
is it feasible to compile the kernel on-device? or does it _have_ to be cross-compiled?
<rapha>
ah, okay ... i do have manjaro on the laptop
<xdarklight>
compiler instructions are the same except: s/arm-linux-gnueabihf-/arm-none-eabi-/
* rapha
wanders off to give it a go
<rapha>
xdarklight: hmm, the feature support table lists eMMC support on S805 as "partial" ... what does that mean? :)
<xdarklight>
rapha: I'll update that. it should say that we have partial SDIO support
<xdarklight>
yes, please clone from kernel.org directly
<rapha>
oooh
<rapha>
cool
<rapha>
in that case no reason not to go for 5.15
<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?
<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 ;)
<xdarklight>
there's no mainline u-boot for these older SoCs currently
<rapha>
wow, that clone is still going on. i do hope it's the right repo :)
<rapha>
time to make some food then
<xdarklight>
yep, that's the correct repo
<rapha>
cool thx!
<rapha>
xdarklight: out of curiosity, what's with the dash after arm-non-eabi?
<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
<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
Ballerburg9005 has quit [Ping timeout: 256 seconds]
<rapha>
oh okay, that's neat then
cmeerw has quit [Ping timeout: 258 seconds]
<rapha>
it finished building
<rapha>
sooo if i'm feeling adventurous, i'll just replace the old uImage with the new one, reboot, and see what'll happen?
<rapha>
got no UART here right now anyways...
* rapha
will go for it. if it doesn't work, can always stick the eMMC into the laptop, but maybe better tomorrow
sputnik_ has joined #linux-amlogic
<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
<rapha>
ah, wait, the kernel build produced a meson8b-odroidc1.dtb, that sounds even _more_ appropriate
<rapha>
and also the hex addresses to the bootm command don't match
<rapha>
your howto has three
<rapha>
my boot.ini has a range
<rapha>
hmm, that range covers your three though
<rapha>
maybe you have three because you have that cpio file, too, which i don't have
<rapha>
and then maybe my range is not a range at all, but it says "address, nothing, anotheraddress"
<rapha>
and no fatload for me, but ext4load
<rapha>
it just seems that the alarm ppl set things up differently
Ballerburg9005 has joined #linux-amlogic
<rapha>
hmm, can't learn anything without making mistakes, and tomorrow i'll go fetch the UART anyways. here goes nothing.
<rapha>
hmm, okay, didn't work :P
<rapha>
see you once I find that UART, xdarklight :)
warpme_ has quit [Quit: Connection closed for inactivity]
Ballerburg9005 has quit [Ping timeout: 252 seconds]