| - thejevans (QUIT: Ping timeout: 255 seconds) (~m-7r3qil@user/jevans) | 00:07 | |
| + thejevans (~m-7r3qil@user/jevans) | 00:08 | |
| + schalken (~schalken@117-118-178-69.gci.net) | 00:09 | |
| elb | minute: oh yeah that was also my conclusion, but my conclusion was that since it seems to be at init, I doubt reform-power-daemon can help with that particular problem | 00:38 |
|---|---|---|
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.0.44) | 01:00 | |
| + Ar|stote|is (~linx@149.210.0.44) | 01:09 | |
| - violet (QUIT: Quit: leaving) (~vi@user/meow/violet) | 01:13 | |
| aloo_shu | if it can be done with a commandline parameter, modinfo for the gpu driver(s) would tell, wouldn't it | 01:38 |
| aloo_shu | josh merely suggested that reform-power-daemon could later tune the gpu back up | 01:40 |
| aloo_shu | checking batteries for bad eggs, or, silly as it sounds, checking if contacts are clean and tight | 01:46 |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 02:30 | |
| + oliverD (~Thunderbi@user/oliverd) | 02:31 | |
| - stephano (QUIT: Quit: Textual IRC Client: www.textualapp.com) (~stephano@71.238.14.13) | 02:35 | |
| - oliverD (QUIT: Read error: Connection reset by peer) (~Thunderbi@user/oliverd) | 02:57 | |
| - thejevans (QUIT: Ping timeout: 265 seconds) (~m-7r3qil@user/jevans) | 03:38 | |
| + thejevans (~m-7r3qil@user/jevans) | 03:39 | |
| - paperManu (QUIT: Ping timeout: 276 seconds) (~paperManu@204.244.186.187) | 03:46 | |
| - thejevans (QUIT: Ping timeout: 255 seconds) (~m-7r3qil@user/jevans) | 03:50 | |
| - paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@204.244.186.187) | 03:50 | |
| + thejevans (~m-7r3qil@user/jevans) | 03:52 | |
| + paperManu (~paperManu@79.127.134.53) | 03:52 | |
| - paperManu (QUIT: Ping timeout: 248 seconds) (~paperManu@79.127.134.53) | 03:59 | |
| + paperManu (~paperManu@79.127.134.53) | 04:01 | |
| - shebang_ (QUIT: Ping timeout: 252 seconds) (~shebang@136.51.81.5) | 04:05 | |
| - paperManu (QUIT: Read error: Connection reset by peer) (~paperManu@79.127.134.53) | 04:20 | |
| - ephase (QUIT: Read error: Connection reset by peer) (~ephase@82.66.198.11) | 05:01 | |
| - Gooberpatrol66 (QUIT: Ping timeout: 246 seconds) (~Gooberpat@user/gooberpatrol66) | 05:17 | |
| + ephase (~ephase@82.66.198.11) | 05:24 | |
| - lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah) | 06:05 | |
| + lidstah (~lidstah@gateway/tor-sasl/lidstah) | 06:06 | |
| + violet (~vi@user/meow/violet) | 06:06 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 06:14 | |
| - lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah) | 06:19 | |
| + lidstah (~lidstah@gateway/tor-sasl/lidstah) | 06:20 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:03 | |
| + andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net) | 11:28 | |
| - pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0) | 11:42 | |
| + pomel0 (~pomel0@user/pomel0) | 11:42 | |
| - mjw (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org) | 12:03 | |
| * Guest1706 -> mjw | 12:26 | |
| + paperManu (~paperManu@204.244.186.187) | 12:32 | |
| - murphnj (QUIT: Quit: murphnj) (~murphnj@user/murphnj) | 14:42 | |
| + murphnj (~murphnj@user/murphnj) | 14:49 | |
| + paperManu_ (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 14:57 | |
| elb | I groveled through the source a little bit and I don't see where there's an opportunity to change the clock speed before the clock structure is passed to the relevant init routine | 15:02 |
| elb | but I'll check modinfo in a bit, that's a good idea | 15:02 |
| elb | there are several different systems at play and I'm not sure I understand how they all plug together | 15:03 |
| minute | elb: i was thinking opps in device tree maybe | 15:13 |
| minute | elb: also, maybe there's a way to change the default freq governor for the gpu | 15:13 |
| + AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net) | 16:19 | |
| - aelius (QUIT: Ping timeout: 244 seconds) (~aelius@user/aelius) | 16:40 | |
| + siviq (~siviq@user/siviq) | 16:44 | |
| - siviq (QUIT: Client Quit) (~siviq@user/siviq) | 16:44 | |
| + aelius (~aelius@user/aelius) | 17:00 | |
| - AnimaInvicta (PART: !!unknown attribute: msg!!) (~AnimaInvi@88-120-179-216.subs.proxad.net) | 17:04 | |
| - paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 17:18 | |
| + paperManu_ (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 17:20 | |
| + shebang_ (~shebang@136.51.81.5) | 17:58 | |
| - amospalla (QUIT: Ping timeout: 264 seconds) (~jordi@user/amospalla) | 18:57 | |
| + amospalla (~jordi@user/amospalla) | 18:59 | |
| josch | minute: about the keyboard version and lpc apiv3: MichaK from the forum had experienced problems earlier and is running a custom build of the keyboard firmware (built from git commit 0c9df04 according to the OLED) but says that this is still the original condition -- could it be that MNT flashed non-tagged keyboard firmware for some of the classic Reforms? | 19:17 |
| josch | see https://community.mnt.re/t/battery-indicator-after-update-upgrade-and-shutdown/4298/12 | 19:17 |
| + mark_ (~mjw@gnu.wildebeest.org) | 19:56 | |
| - paperManu_ (QUIT: Ping timeout: 245 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 20:27 | |
| - mesaoptimizer (QUIT: Quit: WeeChat 4.7.1) (~user@user/PapuaHardyNet) | 20:30 | |
| + mesaoptimizer (~user@user/PapuaHardyNet) | 20:30 | |
| - mjw (QUIT: Killed (osmium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 20:40 | |
| * mark_ -> mjw | 20:40 | |
| + Guest7913 (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 20:40 | |
| - amospalla (QUIT: Ping timeout: 248 seconds) (~jordi@user/amospalla) | 21:04 | |
| + amospalla (~jordi@user/amospalla) | 21:12 | |
| - shebang_ (QUIT: Quit: Konversation terminated!) (~shebang@136.51.81.5) | 21:52 | |
| - andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net) | 21:53 | |
| + paperManu_ (~paperManu@204.244.186.187) | 22:03 | |
| + Guest79 (~Guest79@2a03:7845:2c5:101:d3d8:6a1a:147b:186b) | 22:53 | |
| - Guest79 (QUIT: Client Quit) (~Guest79@2a03:7845:2c5:101:d3d8:6a1a:147b:186b) | 22:53 | |
| - pomel0 (QUIT: Ping timeout: 244 seconds) (~pomel0@user/pomel0) | 22:54 | |
| minute | josch: yes, very possible | 22:55 |
| + _justin_kelly4 (~justinkel@user/justin-kelly/x-6011154) | 23:02 | |
| - _justin_kelly (QUIT: Ping timeout: 264 seconds) (~justinkel@user/justin-kelly/x-6011154) | 23:03 | |
| * _justin_kelly4 -> _justin_kelly | 23:03 | |
| josch | minute: then your theory of a "custom firmware" being the culprit might've been spot-on because if you build a custom firmware (i.e. you are not building a tagged release) then the version string will look like this: g0de4e2e (for git commit 0de4e2e) and only if you build a tagged release it will be, for example: 20250701 (for the latest tag) | 23:06 |
| - bleb (QUIT: Ping timeout: 248 seconds) (~cm@user/bleb) | 23:18 | |
| josch | minute: lpc/reform2_lpc.c calls kstrtou32() to convert the version string to an integer but that will fail for version strings like "g0de4e2e" and the code is not checking the return value of kstrtou32 at all. Maybe this would be better: https://source.mnt.re/reform/reform-tools/-/merge_requests/166/diffs?commit_id=dbf149c162a4cfd7bad395b2a186ea98f86023c5 | 23:20 |
| josch | minute: Is it intentional that choosing the correct api version requires building a git tag? It means that people doing local custom builds need to be careful to tag their experiments or otherwise they will not have apiv3 enabled. | 23:22 |
| + bleb (~cm@user/bleb) | 23:29 | |
| + siviq (~siviq@user/siviq) | 23:32 | |
| - siviq (QUIT: Client Quit) (~siviq@user/siviq) | 23:35 | |
| minute | josch: yeah, that's what i thought about weird string to number conversion | 23:57 |
| minute | josch: the local build actually does another weird thing afaik. it makes a MMDD version instead of YYMMDD | 23:57 |
| minute | sorry, instead of YYYYMMDD | 23:57 |
| minute | josch: your fix looks good. | 23:59 |
| josch | it's not really a fix though | 23:59 |
| josch | like, it probably makes things better but i think there might be a more fundamental problem | 23:59 |
| minute | josch: afaik the g-id happens only in CI | 23:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!