| Wizzup | ok | 00:04 |
|---|---|---|
| Wizzup | those are in uvos branch | 00:04 |
| arno11 | ok cool | 00:05 |
| Wizzup | I'll try to build another kernel tomorrow based on his branch | 00:05 |
| arno11 | ok | 00:06 |
| arno11 | that's already good news that n900 and d4 boot fine | 00:08 |
| Wizzup | yeah, but the d4 calls not working is a PITA :D | 00:09 |
| arno11 | yeah lol | 00:10 |
| sicelo | btw, might be of *some* interest to fmg, uvos, and Wizzup : there's this https://lore.kernel.org/linux-input/ZkKQoTq2xyNvJlHE@google.com/T/#t | 12:02 |
| sicelo | phosh people are behind it ... but who knows ... maybe as we support more devices, might be useful for us too | 12:03 |
| Wizzup | yeah I am not quite sure how this should work from kernel side either | 12:03 |
| sicelo | i must confess i haven't followed it much myself ... | 12:04 |
| sicelo | it might not be about kernel itself ... but more for kernel to report that *this* particular key is a wakeup (or non-wakeup) key | 12:06 |
| Wizzup | oh, I was thinking that this would not emit certain keys when inhibited or something | 12:07 |
| Wizzup | I guess that doesn't make sense | 12:07 |
| sicelo | then userspace takes appropriate action (e.g. unblanking, or refusing to unblank). i think the idea here is that for different phones, you might want key X to wake you up, but on another one, the same key should not wake you up | 12:08 |
| Wizzup | *shrug* I guess | 12:08 |
| Wizzup | I mean isn't it obvious that the volume keys should not wake up the device | 12:08 |
| sicelo | :-P | 12:08 |
| sicelo | for maemo it's obvious | 12:08 |
| sicelo | but think of the way things are for many other phones ... the phone will suspend to ram after a while | 12:09 |
| Wizzup | well it seems to be like the keys should still wake up the device, then it can decide how to handle it | 12:09 |
| sicelo | yes it's an interesting problem, i guess. | 12:10 |
| Wizzup | yeah I think we've got it solved for us for now at least | 12:13 |
| sicelo | i think this is where it all started - https://gitlab.gnome.org/World/Phosh/phoc/-/issues/363 | 12:38 |
| sicelo | so those capacitive keys don't (wouldn't) cause wakeups for us currently? | 12:38 |
| * sicelo suddenly doesn't remember what happens on D4 | 12:38 | |
| Wizzup | that is right, we disable the ts | 12:44 |
| sicelo | yes. i think the keys are a 'second' ts, or something? there was something to that effect i seem to recal | 12:46 |
| sicelo | anyway for d4, i think the problem was handled in the driver for those keys, specific to mapphones. iiuc, this patch is basically handling the same problem, but (hopefully?) in a generic way | 12:49 |
| Wizzup | the second ts is an unrelated issue though | 12:53 |
| Wizzup | as in not related to this | 12:53 |
| sicelo | been a bit stuck on a few IRL stuff and didn't have time for L5 ... hope to get back to it soon | 15:00 |
| sicelo | so if your debian packaging contains: debian/patches/*.patch, the build stuff knows to automatically apply all of them before build starts? or you need some instruction? | 15:07 |
| Wizzup | I think you also need debian/patches/series but I always find that a real PITA so I try to avoid it personally | 15:15 |
| sicelo | ah, ok | 15:17 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!