00:05 <endrift> yay got my pinebook pro

00:05 <endrift> boo ships with an ancient LTS

00:05 <anarsoul> :)

00:06 <endrift> what distro should I use that I can actually use panfrost with?

00:06 <anarsoul> endrift: ping me if you make dts for it earlier than monday-tuesday

00:06 <endrift> I have a dtb for like 4.4.190 or something but that's not uhh new enough

00:06 <endrift> I need to find the dts for it

00:07 <anarsoul> that likely doesn't use mainline bindings

00:07 <anarsoul> bsp kernel is somewhere on mrfixit2001's github

00:08 <anarsoul> https://github.com/mrfixit2001/rockchip-kernel

00:09 <anarsoul> https://github.com/mrfixit2001/rockchip-kernel/blob/release-4.4/arch/arm64/boot/dts/rockchip/rk3399-pinebookpro.dts

00:09 <endrift> I found this https://github.com/ayufan-rock64/linux-mainline-kernel/releases/tag/5.4.0-rc1-1120-ayufan

00:11 <endrift> Does panfrost work with X.org or should I just use Wayland?

00:12 <TheCycoONE> Works with X

00:13 <endrift> Cool, I've had bad luck with Wayland and uh most programs I use

00:14 <endrift> It ships with debian 9, ughhh

00:14 <endrift> I shouldn't try to upgrade to 10

00:14 <anarsoul> :)

00:16 <endrift> this keyboard has...issues

00:16 <endrift> and I don't mean the layout

00:19 <anarsoul> as far as I know there's an issue with touchpad, i.e. keyboard won't respond if you put a finger (or rather a palm) on touchpad

00:19 <anarsoul> but it'll be fixed with firmware update for keyboard/touchpad controller

00:20 <endrift> that might be what it is

00:21 <endrift> I had suspected that might be what was going on but couldn't confirm

00:24 <endrift> I think I might let this sit in a drawer until Manjaro-ARM ships a Pinebook Pro release

00:24 <endrift> :P

00:24 <anarsoul> haha

00:25 <anarsoul> I think I'll get archlinux running on it sometime next week

00:25 <endrift> let me know how that goes, I may want to do that too

00:25 <endrift> or rather, instead

04:44 <endrift> anarsoul: if you end up making a PKGBUILD for the pinebookpro kernel/devicetree, please send it my way. Would love to use it

04:45 <anarsoul> OK

17:40 <narmstrong> tomeu: for ci speed up i wonder if we could use the lava boards as gitlab runners using a custom docker+machine to boot a board to spawn a gitlab job on demand, this would give much more accurate wait and run times, and it would simplify the gitlab ci, except the kernel selection :-/

18:01 <daniels> narmstrong: *raises eyebrow*

18:01 <daniels> i guess the main issue with that is that you can no longer share boards between mesa and kci, which may or may not be a problem for you

18:02 <daniels> but then as I just said to robclark, you do have to do device health monitoring yourself, which can suck a bit

18:05 <narmstrong> daniels: with docker+machine the docker instances are still on-demand, no ? So we would still need to wait until the board is started with the right docker image through lava

18:06 <daniels> oh, i see what you mean ... tbh I haven't really used docker-machine at all, but I've heard largely not-good things about it

18:06 <daniels> but don't let me stop you from trying it out if you're interested :)

18:06 <narmstrong> I’ll investigate how we can speed up and fix our lava issues anyway

18:08 <daniels> how many jobs do you take in parallel? we've just taken the approach of taking like 64 mesa jobs simultaneously and submitting them all to lava, so we don't have to think too hard about balancing between mesa and lava, and different classes, etc