00:39 <DanaG> The big blocker for me on Chromebooks is the keyboard. No super key, no home/end/pageup/pagedown. Alt+up to get pageup is not satisfactory, because how do you do alt-pageup? Alt+alt+up?

00:42 <steev> they're known, yes, they don't affect anything crafty

00:56 <robclark> DanaG: re: cb keyboard.. well I use cb for all corp / non-upstream stuff, plus $day_job devel/test/debug.. and you get used to it.. I'm not sure I'd make the same decisions but I will say it is a big improvement over annoying things on non-cb laptops like ctrl/fn swapping around.. maybe not a big deal if you don't swap devices as much as I do (for testing/debug driver stuff) but IMO the end result is better (ie. easier to just

00:56 <robclark> learn the different shortcuts than learn different kb layouts)

01:38 <craftyguy> steev: ah ok, thanks :)

01:44 <steev> robclark: heh, that actually happens between the c630/flex5g/thinkpad - i can't recall which ones have it in the same spot, but at least, you CAN go into bios and swap it)

01:44 <steev> or at least, i think you can

03:31 <clover[m]> You can swap fn and ctrl in bios on thinkpad yeah

03:32 <HdkR> Unless that option doesn't work like Joshua's

03:33 <HdkR> Completely borks fn and ctrl when enabled on their X13s, which is wacky

13:32 <_[m]1> can't seem to login to steam did anyone succeed?

13:37 <enyalios> i was eventually able to log in by using the steam app to scan the qr code

13:37 <enyalios> that also took a bunch of tries but eventually worked, _[m]1

14:35 <mani_s> broonie, do you consider a cmdline parameter to disable turning off unused regulators in regulator_init_complete()? this would be useful while debugging as most of the time, if there is an issue with the consumer (say display) then the panel regulator gets turned off, resulting in black screen

14:36 <mani_s> Or how about moving it to sync_state?

14:37 <javierm> mani_s: I think a couple of times this question has came up before, something akin to clk_ignore_unused or pd_ignore_unsed but broonie didn't want that?

14:38 <mani_s> hmm. I do think it of a valid debugging thing. Because, what can we do if the display goes off in a laptop?

14:42 <javierm> mani_s: preaching to the choir :)

17:41 <mani_s> javierm, :)

17:49 <steev> obviously you plug in the external monitor that also doesn't work yet :P

17:53 <DanaG> Which of the ARM Chromebooks have the best performance in things like desktop window manipulation, browsing, and scrolling? And do any of them support 4k 120hz display output?

18:05 <robclark> I don't think any will do 4k 120hz.. otherwise, desktop UI isn't very demanding so anything non-ancient should be fine

18:13 <HdkR> Obviously we just need an sc8380xp chromebook so it can do three external displays at 4k120 :)

18:59 <steev> jhovold: i went back through my kernel log, i have only seen bluetooth fail about once a month, last time it failed was 08 October, which was rc5

19:14 <broonie> mani_s: javierm: I don't recall anyone suggesting that before? Anyway, send a patch.

20:12 <javierm> broonie: I'm pretty sure that I suggested you before :) But sure, I'll try to write a patch on Monday

20:36 <broonie> I mean, I'm not thrilled with the likelihood that people are just going to shove it on the command line and not bother.

20:40 <javierm> broonie: I think that was your answer at a time. And if someone want to workaround broken drivers, they could patch the DT and add an always-on

20:56 <DanaG> I'm curious, which is more usable, either with the built-in containers or with natively-installed Linux: a Qualcomm Chromebook, or a Mediatek one?

20:56 <DanaG> Or Rockchip?

20:57 <jenneron[m]> DanaG: probably qcom because of GPU

20:58 <jenneron[m]> as it supports Vulkan 1.3 and OpenGL 4.6

20:58 <jenneron[m]> otherwise they are all well supported probably except mt8192/mt8195 which are work in progress

21:01 <DanaG> Can you do native install on the Qualcomm ones?

21:01 <jenneron[m]> yes

23:44 <DanaG> Any particular model recommendations? Screen quality is important to me.