jaeger changed the topic of #crux-arm to: CRUX-ARM 3.7 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-7 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<r0ni> opt-arm64/libtheora (3.8) missing sig
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ opt-arm64/3.7 ]: libtheora: add .signature
crux-arm-bot has left #crux-arm [#crux-arm]
<r0ni> epic response time ;)
<cruxbridge> <pitillo (@pitillo:crux.nu)> on the way 3.8 :D
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ opt-arm64/3.8 ]: libtheora: add .signature
crux-arm-bot has left #crux-arm [#crux-arm]
<r0ni> so xorg-xf86-video-vesa is broken and i think it's broken on 3.7 and 3.8, i treid some cflags arch has but they didn't help... it's really hard to build things that dep on xorg when xorg won't build
<r0ni> i personally install a dummy package to move on with life but i'm noticing errors with scaling in xfce now on a high res monitor that aren't happening in other distros... and I wonder if this package is to blame
<r0ni> i think xorg needs some help on arm but i'm not 100% on what really needs to be minimally installed
<cruxbridge> <pitillo (@pitillo:crux.nu)> r0ni: if I remember right, on ARM is better to install fbdev instead of vesa
<cruxbridge> <pitillo (@pitillo:crux.nu)> at least to get soft render and full compat
<cruxbridge> <pitillo (@pitillo:crux.nu)> after it, depending on the soc there are alternatives like mali, but last time I played with it I got only working right on the cubieboard
<jaeger> mali gpus seem like nightmares to get working sometimes
<cruxbridge> <pitillo (@pitillo:crux.nu)> I've only got one with full HW support.... the rest was impossible for me... but it was long time ago
<cruxbridge> <pitillo (@pitillo:crux.nu)> probably things haven't changed so much since then xD
<jaeger> yeah
<jaeger> I think I'll try to figure out how to get crux on the orange pi 3b I have
<jaeger> Not worried about the rootfs since we have generic ones available but I know nothing about its u-boot setup yet
<cruxbridge> <pitillo (@pitillo:crux.nu)> ummmm if you want an optimized rootfs for the H6 should take more than 2h here xD
<jaeger> nice that it has an m.2 slot
<cruxbridge> <pitillo (@pitillo:crux.nu)> and 3.8 should be fine
<cruxbridge> <pitillo (@pitillo:crux.nu)> it's another small beast
<jaeger> H6?
<cruxbridge> <pitillo (@pitillo:crux.nu)> about the bootloader.... I've been reading all the afternoon about uboot and extlinux....
<cruxbridge> <pitillo (@pitillo:crux.nu)> isn't the Allwinner H6 the SOC?
<jaeger> RK3566
<cruxbridge> <pitillo (@pitillo:crux.nu)> ah, I mixed the model then
<jaeger> No worries
<cruxbridge> <pitillo (@pitillo:crux.nu)> I can prepare an updated 3.8 optimized rootfs
<cruxbridge> <pitillo (@pitillo:crux.nu)> if you want to avoid rebuilding 3.7/3.8 on the toy... if you want to check performance, it can be a good test
<jaeger> I would probably build it on the m4 mini :) But we shall see
<cruxbridge> <pitillo (@pitillo:crux.nu)> yeah, that was my idea...
<cruxbridge> <pitillo (@pitillo:crux.nu)> but not sure if that's possible as it's a RiscV..... so no way to make a native build, no?
<jaeger> What? Where's riscv in this? I'm confused, heh
<jaeger> The RK3566 is a 4 core cortex A55
<cruxbridge> <pitillo (@pitillo:crux.nu)> so what am I reading....
<cruxbridge> <pitillo (@pitillo:crux.nu)> xD
<jaeger> no idea, heh
<cruxbridge> <pitillo (@pitillo:crux.nu)> jajajajaja
<cruxbridge> <pitillo (@pitillo:crux.nu)> I need to stop
<cruxbridge> <pitillo (@pitillo:crux.nu)> enough for today
<jaeger> sorry for the confusion
<cruxbridge> <pitillo (@pitillo:crux.nu)> the datasheet confirms it's a 4 core corstex A55 with neuronal PU.....
<cruxbridge> <pitillo (@pitillo:crux.nu)> well, I think I was a bit confused.... but the more I read, the more I love this world....
<jaeger> I get confused all the time, no worries
<cruxbridge> <pitillo (@pitillo:crux.nu)> RISC-V MCU found inside the Rockchip RK3566 SoC
<cruxbridge> <pitillo (@pitillo:crux.nu)> amazing SOC btw
<cruxbridge> <pitillo (@pitillo:crux.nu)> check the MCU and the mailbox communication between cores
<cruxbridge> <pitillo (@pitillo:crux.nu)> this is growing very fast
<cruxbridge> <pitillo (@pitillo:crux.nu)> the MCU has its own JTAG.... if I understood it right, it's an embedded RiscV core inside the SOC
<jaeger> Ah, I found the H6 reference, looks like the Orange Pi 3 (not 3b) was an H6
<jaeger> I have the 3b
<cruxbridge> <pitillo (@pitillo:crux.nu)> yeah, that was my error... I mixed the models (forgot the rev)
<cruxbridge> <pitillo (@pitillo:crux.nu)> * (I forgot
<jaeger> No worries, I didn't know until now, learning :)
<r0ni> yeah tho, i'm saying we maybe need to make a arm specific xorg meta port, cuz it wants xf86-video-vesa and it makes everything fail along the way until you make it happy
<r0ni> i dont actually have problems with video output, just installing ports when half the chain fails... maybe we can just replace vesa with fbdev on arm?
<jaeger> I wonder how to actually get a serial connection working on the orange pi 3b, just getting junk no matter which settings I've tried
<jaeger> Ah, maybe my PL2303 usb serial adapter can't do 1500000 speeds