13:15 <ccaione> hi. I'm still playing with u-boot and a rk3288 based chromebook. Chainloading u-boot from the bootrom code (coreboot / depthcharge ?) works perfectly fine (as described in README.chromium). I was now wondering if I can bypass / substitute the bootrom code at all, booting straight from SD (yes, I have a servo board if that's needed). Honestly README.rockchip is a bit vague in that sense.

16:11 <mmind00> maz: oh wow ... that drm stuff is a rabbits hole ;-) ... looks like the 43-patch behemoth depends on some more patches I just tracked down

17:03 <maz> mmind00: yeah, it is crazy. I've stayed clear of it and did my own, one at a time fixes.

17:04 <eballetbo> mmind00: I think that depends on this https://lkml.org/lkml/2018/1/10/682 , /me is also getting crazy on these (to much patches :P)

17:04 <eballetbo> s/to/too

17:04 <mmind00> eballetbo: yep, these are the ones I found

17:06 <maz> mmind00: what annoys me the most is that while this series grows to no end, we have bugs in mainline that are not getting plugged ("we're rewriting all of this").

17:09 <eballetbo> shouldn't we concentrate first on fix current bugs?

17:11 <mmind00> eballetbo: likely, which is why I'm looking at these 2 series now :-)

17:18 <eballetbo> mmind00: one patch that I'd like to see merged as fix in this release cycle is: https://patchwork.kernel.org/patch/10205807/

17:19 <eballetbo> mmind00: In the commit notes I say that is applied on top of the 43-patches but looking again I think that doesn't depend on it

17:20 <eballetbo> mmind00: and that's a fix for s2r backlight problem /me checks again

18:00 <eballetbo> yeah, doesn't depends on the series and applies cleanly without these