00:54 <steev> no u

00:55 <steev> but also, thanks for the reminder, that bit bamse and i while testing the next stuff

00:56 <steev> robclark: does it have to be =y or can it be m?

00:57 <robclark> I think it can be =m if you don't need display to probe before you have modules (or if you have modules in initrd).. I'm using =y because that is the easiest thing on a chromebook

00:57 <robclark> it can be whatever PANEL_SIMPLE was before

00:57 <steev> fair, we had that as =m in the aarch64-laptops distro_defconfig

00:57 <robclark> ok, then =m should be fine

00:58 <steev> asjdfl;asjkdf;laksjdf

00:58 <steev> this friggin bluescreen

00:58 <robclark> it's just to give you that familiar windows experience :-P

00:59 <steev> i know but i'm trying to test thara's patches for cpufreq - it LOOKS like we get 2.96GHz finally :D

00:59 <steev> just that the past 5 boots now i've gotten the blue screen

00:59 <steev> not a HUGE issue because i can just close the display and then open after it suspends and it's "fine" minus the spam of the dmesg

01:00 <steev> just frustrating to run into so many boots in a row

01:00 <steev> also frustrating because ssh in and running reboot doesn't always properly disconnect before shutting down so the local terminal is in a hung state

01:26 <steev> blargh

01:26 <steev> as soon as i sent the email.... it worked the next boot

03:09 <steev> bamse: is something wrong with patchwork? does it only get patches if it's not cc? i'm not seeing lumag's clk patch

03:09 <steev> i also had to go and get thara's patches manually too

03:17 <bamse> steev: odd, i've not had any problems recently :/

03:33 <steev> hm, i see it in the web interface

03:33 <steev> well, i see lumag's in the web interface, but not thara's

03:33 <steev> https://patchwork.kernel.org/project/linux-arm-msm/list/?param=2&page=1

03:45 <bamse> steev: ahh! "Action Required"

03:45 <steev> oh!

03:46 <bamse> steev: i went through the list earlier today and flagged most things that i won't merge as "Not Applicable"

03:46 <bamse> steev: so it won't show up in that view

03:46 <steev> got ya

04:45 <steev> i don't wanna speak too soon, but i haven't gotten the bluescreen since i added lumag's clock patch in

04:46 <steev> ah perfect timing, after i said it, i got one

13:40 <macc24> robclark: well.. i was about to

13:41 <macc24> but Dylanger(cadmium user) beat me to it and ported cadmium to homestar https://i.imgur.com/S7RIKvx.png

13:42 <macc24> robclark: that config option is needed for pretty much all other chromebooks too... except krane

13:42 <macc24> and couple others

13:43 <macc24> currently i'm re-doing emmc installation in cadmium... would probably need to re-do it again though

13:45 <macc24> all cadmium devices now *should* bootup on 5.16 kernel

13:50 <macc24> basically i'm going to shove entire cadmium everything into cadmium image to build cadmium onto emmc itself xDD

13:50 <macc24> cadmium recursion

15:45 <robclark> macc24: oh, nice.. I think homestar was the one that we were a bit late on getting dts upstream.. I think patches were posted before it started shipping but only land in v5.16

15:45 <robclark> oh, and I guess he is using v5.16

15:46 <macc24> robclark: 5.16-rc1 is quickest kernel release to reach cadmium

15:46 <macc24> :D

15:46 <robclark> :-P

15:46 <macc24> either i became quite good at carrying patches through kernel versions, or there was less stuff happening

15:57 <robclark> at least on the trogdor/strongbad side of things, we are trying to make sure there aren't many patches that need to be carried ;-)

15:59 <macc24> yea

15:59 <macc24> there are no trogdor specific patches in cadmium arm64 kernel