00:31 <amstan> hessophanes: depends what hardware you have

00:32 <amstan> looks like suspend resume is still incomplete, ddr dvfs doesn't work (if you're battery powered this might hurt), do you have an lvds display?

00:32 <amstan> oh, and gpu

00:32 <amstan> oh.. but you're saying it's out of date?

00:33 <amstan> still, i'm surprised that most of that is green, i like it, i should get my board going with 4.19

00:40 <hessophanes> I'm actually still trying to evaluate which hardware to buy. Quite a few DTBs have been merged, and even U-Boot upstream at least knows about the EVB and the Rock960, so I guess the upstreaming efforts are still underway, but I'd still like to know whether I'm locking myself into a vendor tree for some core part of device functionality before I go shopping. ;)

00:41 <hessophanes> I can probably live without suspend and DVFS for now - but I'd rather not lose the option to connect a display...

00:41 <hessophanes> GPU? Meaning I won't be able to get the Mali off the ground with mainline 4.20?

00:42 <hessophanes> (Or were you just citing the matrix?)

00:42 <stikonas> well, there is panfrost, but you still need patched kernel for that

00:46 <amstan> hessophanes: i was just citing the matrix, missed the part where you said the matrix is outdated

00:47 <amstan> my final goal is to have a headless 3399 board running linux-rt

01:00 <hessophanes> Ah, nice, the state of Panfrost looks promising. Thanks for the pointer, I'll check that out. I don't mind patching the kernel...

05:34 <beeble> amstan: we have linux-rt running on rk3399 for about a year

05:36 <beeble> but are you really in need for full -rt? preemtive patches that are available for 4.19 are working well enough for most usecases

07:19 <Ke> had a crash or lockup again on linux-4.20-rc6ish and Kevin

07:20 <Ke> I believe it's plausible that mwifiex_pcie is causing this

07:20 <Ke> the locking is provably broken

10:40 <shadeslayer> has anyone had any luck running the mali proprietary blobs against rockchipdrm?

10:40 <shadeslayer> I hit this https://github.com/rockchip-linux/libmali/issues/20

10:40 <shadeslayer> on the RK3399 Firefly

10:50 <shadeslayer> ah hm, maybe because I'm not in the video group

14:08 <shadeslayer> hessophanes: I'm currently evaluating a Firefly RK3399 btw

14:08 <shadeslayer> hessophanes: so far I've managed to boot the stock debian kernel on it, both HDMI and ethernet work

14:09 <shadeslayer> Got the GPU working with a single patch to the kernel and build fixes to the midgard dkms module

14:59 <tomeu> shadeslayer: does kmscube work with the blob?

14:59 <shadeslayer> tomeu: I'm not sure, but I can start Plasma with it, and es2gears works

14:59 <shadeslayer> Isn't kmscube rendering directly to the DRM API?

15:00 <shadeslayer> I need to debug why armsoc is being stupid slow though

15:00 <shadeslayer> ( modesetting otoh works perfectly fine )

15:07 <hessophanes> shadeslayer: Thanks, that's interesting to know! I'll replicate that build to figure out how bad the patching and fixing is - do you then run the r14p0 rockchip libmali in userland? The DKMS module says it

15:07 <hessophanes> is a r16...

15:08 <shadeslayer> hessophanes: yes, r14p0 userland works with the r16p0 dkms module

15:08 <shadeslayer> hessophanes: https://salsa.debian.org/shadeslayer-guest/mali-midgard is the package I'm working on

15:09 <shadeslayer> I haven't been keeping track of my changes cleanly just yet :)

15:10 <hessophanes> That's ok, I'll inter-/extrapolate. ;) Thanks!

15:13 <shadeslayer> yw

15:14 <shadeslayer> hessophanes: patch for the kernel was this btw https://patchwork.kernel.org/patch/10506169/

15:14 <shadeslayer> I think it'll land in 4.20

15:41 <jaganteki> Hi, anyone have any idea about MIPI CSI2 is Mainline kernel?

15:41 <jaganteki> I have seen the status http://opensource.rock-chips.com/wiki_Status_Matrix

15:41 <jaganteki> but not listed.

15:41 <jaganteki> any patches in ML or anyone working?

15:41 <jaganteki> on rk3399

15:47 <beeble> search for isp1 on patchwork

15:50 <mmind00> jaganteki beeble: and from what I've heared there may be people working on refreshing that patchset to address review comments and new v4l-internal changes since the last version

15:50 <mmind00> but there is no ETA or such

15:52 <jaganteki> look like last version is from March 8

15:56 <jaganteki> mmind00: any idea about next version submission?

15:58 <mmind00> jaganteki: no idea, but activity did start up again recently after being stuck since the last version

15:58 <jaganteki> Okay, thanks.

21:09 <hessophanes> shadeslayer: Found it, it's already been merged (as part of 4.19-rc7), commit 23c7b54ca1cd.