00:22 <apritzel> ah yeah, that's a stupid thing that TF-A introduced: compiling natively still requires a CROSS_COMPILE variable. Join me in complaining about this ...

02:53 <MoeIcenowy> apritzel: oops in this case what should be set for CROSS_COMPILE?

02:53 <MoeIcenowy> CROSS_COMPILE="" ?

03:57 <BroderTuck> MoeIcenowy: in my case it would have been CROSS_COMPILE=aarch64-slackware-linux-gnu- except for that objcopy and objdump still wouldn't have worked since those 2 commands don't have the longname versions on my rootfs

05:11 <junari> Today I remembered that I didn't replace the kernel modules when I copied it to the sdcard. Now my usb wifi module works well with x96qpeo+

05:11 <junari> the board works for some time and can compile packages without any problems

05:31 <junari> But it is slower at compiling packages than opizero3 overclocked to 1.8GHz

06:09 <junari> Maybe it will be useful to someone https://forum.manjaro.org/t/h728-a523-a527-t527-initial-support-thread/173654

10:50 <apritzel> MoeIcenowy: TF-a was changed last year to require a CROSS_COMPILE variable, if that was unset (or empty, same thing), it would look for "aarch64-none-elf-gcc", then give up if that's not found

10:51 <apritzel> two months later they added another fallback, for "aarch64-linux-gnu", the most common triplet

10:52 <apritzel> which fixed the problem for most people running natively, as modern distribution use exactly that triplet - and the fully qualified name also works natively

10:53 <apritzel> but for BroderTuck and me, as the two remaining Slackware users, that's not the case

10:56 <MoeIcenowy> ah I think for the host toolchain, have no triplet prefixed executable is a proper thing

10:56 <MoeIcenowy> (BTW my distro uses alternative triplet too, aarch64-aosc-linux-gnu

10:58 <apritzel> absolutely, I 100% agree, and you wouldn't even need to do anything: just use ${CROSS_COMPILE}gcc everywhere

10:59 <apritzel> but they want to have a preference for this "bare metal toolchain"

12:30 <szemzoa> my small MIPI lcd arrived, and I try to enable the display on V851s. I think it's somehow similar to A133 maybe, just it doesn't have lvds output, just MIPI. This is the current output now: https://pastebin.com/Jytc9iG8 anybody has an idea what I should look for?