**** BEGIN LOGGING AT Sun Jun 03 03:00:02 2018
Jun 03 11:59:25 <kilobyte> so uhm, how am I supposed to wake it from blank screen?
Jun 03 12:00:58 <kilobyte> even normally, I sometimes get the Android overlay blinking in (charging icon and/or blackness), which can be recovered for a split second when on the login screen, no apparent way to recovery (other than hard reboot by holding Esc for 10 seconds) when logged in
Jun 03 12:03:31 <kilobyte> after reboot it's random whether I'll get blinking overlay, or apparently normal functionality -- until the screen gets blanked
Jun 03 12:47:01 <Houoin_Kyouma> What are the chances MTK releases the Linux drivers for the CPU?
Jun 03 13:58:55 <MonkeyofDoom> Houoin_Kyouma: what do you mean? have you looked at the kernel git tree?
Jun 03 14:14:36 <Captain_Harlock[> Has anyone had issues with the bluetooth on their gemini not wanting to stay connected to a headset?
Jun 03 15:53:34 <Houoin_Kyouma> What are the chances MTK releases the Linux drivers for the CPU?
Jun 03 18:33:00 <Captain_Harlock[> Anyone know which version o ExaGear desktop is needed to work on the gemini? They are having a buy1 get 1free sale currently.
Jun 03 19:01:01 <devyl[m]> the armv8 should work
Jun 03 19:01:36 <devyl[m]> https://en.wikipedia.org/wiki/ARM_Cortex-A72
Jun 03 19:07:13 <TheKit> Captain_Harlock[, armv8
Jun 03 19:08:18 <TheKit> means it's possible to get it for 18.73 when splitting the costs?
Jun 03 19:45:31 <MonkeyofDoom> update: I could not get the linaro gcc 7.2.1 toolchain to build a bootable kernel
Jun 03 19:51:06 <TheKit> MonkeyofDoom, that's unfortunate
Jun 03 19:51:23 <TheKit> any pros of using 7.2.1 toolchain over older one to build 3.18 kernel?
Jun 03 19:52:41 <MonkeyofDoom> no, I just get the creeps using known-buggy software ;)
Jun 03 19:53:09 <MonkeyofDoom> I'll try a few other toolchains eventually and see if I can roughly bisect
Jun 03 19:53:40 <MonkeyofDoom> in the meantime I'd like to actually finish my changes to the LED, backlight, and battery drivers since those will improve the debian experience
Jun 03 20:11:00 <TheKit> battery would be surely interesting
Jun 03 20:11:48 <TheKit> I wonder how doable is forward-porting SoC specific drivers either for MediaTek 4.4 fork or mainline
Jun 03 20:31:09 <MonkeyofDoom> a lot of work, but certainly doable
Jun 03 20:31:17 <MonkeyofDoom> I think mainline is the only reasonable target
Jun 03 20:31:57 <MonkeyofDoom> I haven't looked at MediaTek's 4.4 fork, but a) it's 4.4 and b) it's MediaTek ;)
Jun 03 20:32:20 <MonkeyofDoom> their driver devs seem to have some very strange ideas about how to write kernel code
Jun 03 20:33:43 <MonkeyofDoom> generally they seem to abstract over SoC product lines, rather than over actual hardware components, making it impossible to reuse their drivers for other systems with the same components without significant rewrites
Jun 03 20:34:34 <MonkeyofDoom> the Linux Way is to expose hardware component functionality through standard interfaces and only consider configurations like products/SoCs at the devicetree level, which is generally a lot saner
Jun 03 20:35:05 <MonkeyofDoom> the mtk way ends up with nonsense like battery drivers that have tacked-on code for "oh what if there's a second battery"
Jun 03 20:45:56 <MonkeyofDoom> hmmmmm
Jun 03 20:46:11 <MonkeyofDoom> does the gemini actually have a mt6323 PMIC?
Jun 03 20:47:42 <MonkeyofDoom> it has an upstream driver (https://github.com/torvalds/linux/blob/master/drivers/regulator/mt6323-regulator.c) which we could maybe just backport verbatim rather than trying to deal with the `battery_common.c` nonsense mtk provides
Jun 03 20:54:55 <TheKit> MonkeyofDoom, are there likely to be lots of non-MediaTek systems with same components though?
Jun 03 20:55:03 <TheKit> except for maybe touchscreen/LCD/etc
Jun 03 20:57:43 <TheKit> as for mt6323, I can't confirm, but commit says MT7623 has it, which is rougly same age as ours Helio X2x, so either same or similar chip is likely
Jun 03 21:04:30 <MonkeyofDoom> TheKit: no clue, but there's no reason not to make things properly flexible
Jun 03 21:05:14 <TheKit> what I can't understand more is basically them having separate kernel fork for every SoC
Jun 03 21:05:40 <TheKit> (e. g. our kernel generally doesn't include code for other SoCs)
Jun 03 21:06:07 <MonkeyofDoom> it's insane
Jun 03 21:06:22 <MonkeyofDoom> maybe they scale development with separate teams per SoC
Jun 03 21:06:30 <MonkeyofDoom> (that never communicate with each other)
Jun 03 21:09:42 <TheKit> no, they have common code
Jun 03 21:10:09 <TheKit> and their overall custom code architecture over them is very similar
Jun 03 21:11:08 <MonkeyofDoom> ah
Jun 03 21:11:18 <MonkeyofDoom> not sure then
Jun 03 23:00:56 <munchaus1n> Hey guys can anyone clue me in to how to use headphones in linux?
Jun 03 23:07:27 <munchausen> Ah, think they weren't plugged in properly :)
Jun 03 23:10:34 <munchausen> Oh no, it is coming out of both headphones and speakers :(
Jun 03 23:24:38 <sheepbat> does pavucontrol do anything?
Jun 03 23:28:46 <munchausen> Funny you should say, I was just installing it
Jun 03 23:36:04 <munchausen> It doesnt help
**** ENDING LOGGING AT Mon Jun 04 03:00:00 2018