| grimmware | fair | 00:06 |
|---|---|---|
| grimmware | this is a mystery I don't care enough to solve so thanks for the elegant solution <3 | 00:07 |
| antti | =P | 00:10 |
| - ephase (QUIT: Quit: WeeChat 4.4.3) (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 00:23 | |
| - mtm (QUIT: Ping timeout: 252 seconds) (~textual@47.202.75.129) | 01:03 | |
| + mtm (~textual@47.202.75.129) | 01:05 | |
| - cobra (QUIT: Ping timeout: 245 seconds) (~cobra@user/Cobra) | 02:04 | |
| - mjw (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org) | 03:07 | |
| + cobra (~cobra@user/Cobra) | 03:11 | |
| - nsc (QUIT: Ping timeout: 265 seconds) (~nicolas@i5C74DC72.versanet.de) | 03:11 | |
| + nsc (~nicolas@7-99-142-46.pool.kielnet.net) | 03:13 | |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.188) | 03:19 | |
| + aloo_shu (~aloo_shu@85.51.18.219) | 03:22 | |
| - op_4 (QUIT: Remote host closed the connection) (~tslil@user/op-4/x-9116473) | 04:05 | |
| + op_4 (~tslil@user/op-4/x-9116473) | 04:05 | |
| + midfavila (midfavila@sdf.org) | 04:17 | |
| - paperManu (QUIT: Ping timeout: 276 seconds) (~paperManu@107.159.243.8) | 05:01 | |
| - Ar|stote|is (QUIT: Ping timeout: 265 seconds) (~linx@149.210.0.92) | 05:03 | |
| + Ar|stote|is (~linx@149.210.3.150) | 05:07 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.3.150) | 05:32 | |
| + Ar|stote|is (~linx@149.210.3.150) | 05:32 | |
| - Sario (QUIT: Quit: WeeChat 4.3.5) (sario@libera/staff/owl/sario) | 07:10 | |
| - aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@85.51.18.219) | 07:18 | |
| + Sario (sario@libera/staff/owl/sario) | 07:19 | |
| + aloo_shu (~aloo_shu@90.166.98.178) | 07:21 | |
| - Kooda (QUIT: Quit: WeeChat 4.2.2) (~kooda@natsu.upyum.com) | 07:25 | |
| + Kooda (~kooda@natsu.upyum.com) | 07:27 | |
| + glu__ (~glu@user/glu) | 08:19 | |
| - glu_ (QUIT: Ping timeout: 244 seconds) (~glu@user/glu) | 08:20 | |
| - ajr (QUIT: Ping timeout: 276 seconds) (~ajr@user/ajr) | 09:16 | |
| + gustav28 (~gustav@c-78-82-52-90.bbcust.telenor.se) | 10:02 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:05 | |
| + jacobk_ (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:05 | |
| pinsl | I am thinking about backing the reform next and building a custom keyboard for it. As my preferred layout uses a bunch of QMK features I would need to port QMK to the keyboard. I looked at the schematics and saw that the keyboard also does thinks like talking to the system controller. And also the keyboard is powered all the time which means some kind of sleep mode needs to be implemented. | 10:47 |
| pinsl | Did jack humbert release his QMK code anywhere? I can't find it. | 10:47 |
| josch | pinsl: i don't think jack humbert is active here on irc -- did you message them on the forum? | 10:52 |
| pinsl | no, not yet | 10:55 |
| pinsl | I am wondering why the official firmware isn't QMK. Looking at the schematics it looks like the mnt next's keyboard also has to handle the trackpad. QMK has builtin support for this for example. | 11:04 |
| josch | pinsl: the answer is probably: because nobody has done the work :) | 11:23 |
| josch | pinsl: if you search in the logs, there is an answer here: https://mntre.com/reform-irc-logs/2024-10-29.log.html#t23:12:58 | 11:26 |
| pinsl | ah interesting, thanks | 11:28 |
| josch | so i guess if you are familiar with qmk, go for it :) | 11:29 |
| - xha (QUIT: Quit: WeeChat 4.4.4) (~xha@user/xha) | 11:32 | |
| + xha (~xha@user/xha) | 11:34 | |
| pinsl | well, I am not (I just build some custom keyboards like this one: https://git.sr.ht/~pinsl/split-keyboard). But the dream of having a laptop with an ergo keyboard is tempting :) | 11:34 |
| josch | pinsl: wow awesome! And thanks for sharing your work under MIT/Expat :) | 11:45 |
| josch | pinsl: for the Reform Next, note that space is kinda cramped and the keyboard v3 had ist PCB be cut out as much as possible at the sides to make room for the connectors on the PCB for the two side panels | 11:46 |
| josch | pinsl: do you have an account on the forum to write to jack humbert? | 11:48 |
| pinsl | the reform-next repo does not contain the pcb of the keyboard, I just used the keyboard4 in the reform repo as a reference. yeah space is kinda tight I might have to make some changes to my layout but that's fine. | 11:49 |
| pinsl | josch: i sent him an email | 11:50 |
| josch | pinsl: keyboard v4 has the necessary pcb shape for the reform next. That keyboard can be used standalone, in the classic reform as well as in the reform next. | 11:54 |
| - mtm (QUIT: Ping timeout: 260 seconds) (~textual@47.202.75.129) | 13:02 | |
| + mtm (~textual@47.202.75.129) | 13:05 | |
| + mjw (~mjw@gnu.wildebeest.org) | 13:06 | |
| ch | pinsl: from a very recent discussion it'd be super interesting if someone ported ZMK to it | 13:32 |
| pinsl | ch: zmk does not support pointing devices (yet) | 13:32 |
| pinsl | what's the appeal of zmk? | 13:33 |
| ch | proper rtos, which could be reused for the other profucts | 13:34 |
| + paperManu (~paperManu@107.159.243.8) | 14:27 | |
| + chomwitt (~alex@2a02:587:7a09:1500:42b0:76ff:fe46:a5fd) | 15:00 | |
| - glu__ (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 15:29 | |
| + glu_ (~glu@user/glu) | 15:29 | |
| + ephase (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 15:49 | |
| - aperezdc (QUIT: Ping timeout: 276 seconds) (~aperezdc@2a03:6000:6e61:633::43) | 16:12 | |
| - aloo_shu (QUIT: Ping timeout: 264 seconds) (~aloo_shu@90.166.98.178) | 16:34 | |
| + aloo_shu (~aloo_shu@85.51.17.108) | 16:37 | |
| grimmware | finally got wired networking in my new place, great to finally use the industrial ethernet on the pocket! | 17:35 |
| minute | nice | 17:51 |
| + ajr (~ajr@user/ajr) | 17:57 | |
| - ajr (QUIT: Ping timeout: 252 seconds) (~ajr@user/ajr) | 18:04 | |
| minute | my pocket keyboard's rp2040 can get into a state where the reset button is not enough to reset it. it's usb is borked and also blocking the usb hub on the main board (maybe flooding it?) while it is out of reset. only a hard power cycle of 3v3 on the keyboard's supply will make it good again. quite mysterious | 18:09 |
| grimmware | oh wow yeah that's pretty novel. | 18:10 |
| - Ar|stote|is (QUIT: Ping timeout: 265 seconds) (~linx@149.210.3.150) | 18:12 | |
| + Ar|stote|is (~linx@149.210.0.130) | 18:16 | |
| + aperezdc (~aperezdc@46.23.89.43) | 18:17 | |
| minute | thinking a bit more about it, it could be an interaction between the usb hub chip and the rp2040, where the hub gets into a weird state and hangs the re-enumartion of the rp2040 on that port, and the port only becomes properly reset through a power cycle of the device | 18:18 |
| minute | (of the downstream device, the keyboard, i mean) | 18:19 |
| minute | ah cool, i'm able to reproduce this | 18:20 |
| minute | i have this new watchdog code that resets rp2040 if the watchdog is not fed every 100ms. because of a funny bug i can trigger this code just by using the power on function (because the animation takes >100ms). i just have to keep holding hyper+enter to hang the rp2040 after a few tries | 18:21 |
| minute | so that it becomes unresettable | 18:21 |
| minute | the usb hub theory is not correct, as i can disconnect usb and it is still unresettable | 18:22 |
| minute | fascinating that this is possible | 18:23 |
| minute | bizarre https://github.com/raspberrypi/pico-sdk/issues/737 | 18:46 |
| minute | unrelated, but chuckles https://github.com/raspberrypi/pico-sdk/issues/2118#issuecomment-2520362573 | 18:50 |
| minute | did some small changes to uart and uart irq and now i can't get it to hang anymore | 18:57 |
| + ajr (~ajr@user/ajr) | 19:28 | |
| - paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.243.8) | 19:43 | |
| - glu_ (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 19:44 | |
| + glu_ (~glu@user/glu) | 19:44 | |
| pinsl | how fast do the batteries drain when the device is off? on the reform next, the rp2040 on the motherboard is continuously waiting for uart messages and the rp2040 on the keyboard is waiting for the on button to be pressed. wouldn't it be more efficient for example to let the keyboard wake the motherboard using an external interrupt? | 19:48 |
| - glu_ (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 19:51 | |
| + glu_ (~glu@user/glu) | 19:54 | |
| BoostisBetter | minute: any chance I got get that build? | 19:58 |
| BoostisBetter | minute: in the meantime I have drilled a hole in my keyboard cover to make it possible to hit the reset pin without removing the cover. | 19:58 |
| minute | BoostisBetter: yes, i wanted to ask you to test :D here is the build https://source.mnt.re/reform/pocket-reform/-/jobs/7287/artifacts/browse | 20:03 |
| BoostisBetter | minute: Thank you! | 20:09 |
| josch | pinsl: would you like me to make an experiment for you using the classic reform? | 20:10 |
| pinsl | josch: well if noneone has done that before then sure. but the architecture and used chips is quite different on the reform next as far as I understand. | 20:13 |
| josch | pinsl: i cannot remember somebody having really made an experiment, no | 20:13 |
| josch | pinsl: i'm currently using my reform 24/7 to compile linux (bisecting something) so i cannot make a several day long test right now. But i write it down for later. Should i forget, please feel free to ping me about it. | 20:14 |
| pinsl | josch: haha ok sure. don't you expect the lifetime to be several weeks at least? and if not do you always remove the batteries when you store your laptop? | 20:16 |
| josch | pinsl: yes, i'd expect it to be several weeks but if i check how much percent is gone after a week i think we can just extrapolate | 20:17 |
| josch | pinsl: if you do not remove the batteries they will at some point drain empty which is a problem for very old reform classic setups without the protected battery boards | 20:18 |
| BoostisBetter | minute: firmware updated. I will let you know how it is goes. | 20:19 |
| minute | BoostisBetter: thanks!! | 20:19 |
| pinsl | I see that the reform next has a plug for a power switch that would disable the voltage regulator for the system controler. is that intended to be used? | 20:19 |
| pinsl | josch: ah right, ok | 20:20 |
| minute | pinsl: it does? where? | 20:20 |
| minute | *me does git pull at home* | 20:20 |
| pinsl | minute: STANDBY_SHDN | 20:21 |
| pinsl | I justa assumed that's where a power switch would be connected to... | 20:22 |
| pinsl | (J1 POWSW) | 20:22 |
| minute | pinsl: ah yes, forgot about that. it's intended for a very low power mode (i.e. if you want to store the laptop for a longer while) | 20:23 |
| minute | pinsl: or if you need to hard power cycle the system controller | 20:23 |
| minute | on pocket reform we have the same thing, wired to a physical switch on the side | 20:24 |
| pinsl | minute: will the reform next have such a switch? | 20:24 |
| minute | pinsl: maybe, not 1000% sure yet | 20:29 |
| minute | i might combine it into a dual dip switch with camera kill switch (camera kit is optional) | 20:29 |
| BoostisBetter | minute: I know not to bug you or anything, but are the main changes in the build for the kb about the stability of the controller? | 20:30 |
| BoostisBetter | Or was there something else you were targetting as well? | 20:30 |
| BoostisBetter | minute: I mean, I am not trying to bug you | 20:31 |
| minute | BoostisBetter: 100% focusing on the stability question, avoiding those crashes/lockups of the keyboard | 20:39 |
| minute | BoostisBetter: ah, one more thing: i tried to fix/work around the thing where you have to "turn on" 2x | 20:39 |
| BoostisBetter | minute: Yeah I noticed that as well. Was wondering if you knew about the 2x power on thing. I am using my pocket ALL the time, so I will let you know how it is going. I now believe that my Pocket has rarely ever really crashed. I was blaming LibreOffice a lot, but it wasn't the issue. I'm at a point now where the Pocket is super rock solid. So I really appreciate all of the hard work you are putt | 20:41 |
| BoostisBetter | ing into this little marvel. | 20:41 |
| BoostisBetter | minute: I don't ned to reboot after flashing the keyboard do I? I just psuspended and resumed about 25 minutes later, and the keyboard was not responsive and no OLED. I just reset the kb and am up and running again. | 20:42 |
| minute | BoostisBetter: hmm ok i need to look into this psuspend business, i haven't tried it so far. can you point me to which script you are using? (link) | 20:43 |
| BoostisBetter | minuet: you bet. One second. | 20:44 |
| BoostisBetter | minute: if you go here and scroll down psuspend is the first script listed with how to 'install' it. | 20:44 |
| BoostisBetter | https://github.com/amospalla/reform | 20:45 |
| minute | BoostisBetter: thx | 20:48 |
| - jacobk_ (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 21:00 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 21:00 | |
| BoostisBetter | minute: fyi I am running ch's sysctrl firmware and I haven't seen anymore T timeout on the OLED. | 21:13 |
| minute | BoostisBetter: ok cool. so the T were coming from a regular check for "is the system powered on" by the keyboard that is not really necessary and which i removed | 21:13 |
| BoostisBetter | minute: also one other thing I noticed when updating the keyboard check was the the script was failing to validate the install file. I commented that out, and it flashed the firmware no issue from that point on | 21:14 |
| BoostisBetter | the file path looked correct though and I check permissions on the file which I would assume doesn't matter because I was running the script with sudo | 21:15 |
| minute | BoostisBetter: ah yes, that's possible | 21:16 |
| - aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.108) | 21:35 | |
| + aloo_shu (~aloo_shu@90.166.98.126) | 21:38 | |
| - glu_ (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 21:44 | |
| + glu_ (~glu@user/glu) | 21:44 | |
| + reform13903 (~shard@2601:646:8f89:e680::563a) | 21:52 | |
| - bpye (QUIT: Quit: The Lounge - https://thelounge.chat) (~bpye@user/bpye) | 22:12 | |
| BoostisBetter | minute: so far after reseting the kb controller right after flashing the controller, I have had zero issues. I havs psuspended twice during that time. | 22:15 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-90.bbcust.telenor.se) | 22:15 | |
| BoostisBetter | minute: I think it is still too early to tell but I am just letting you know as we go here. | 22:15 |
| BoostisBetter | minute: I can type on the Pocket now with nearly any issues. Great little computer for sure. Really looking forward to to RK upgrade. | 22:16 |
| minute | BoostisBetter: thanks for reporting! ah yeah, you're still on 8mp! | 22:17 |
| BoostisBetter | minute: genau | 22:17 |
| minute | BoostisBetter: i think rk3588 will feel like quite the upgrade :D | 22:17 |
| BoostisBetter | minute: if I am being honest I think this SoC is really not bad. I understand moving beyond it of course. I am really looking forward to my little monster upgrade kit though. It is going to be a beast then. | 22:18 |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-126-1-93.tukw.qwest.net) | 22:25 | |
| + colinsane (~colinunin@97-126-1-93.tukw.qwest.net) | 22:30 | |
| - ephase (QUIT: Quit: WeeChat 4.4.3) (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 22:40 | |
| - colinsane (QUIT: Ping timeout: 260 seconds) (~colinunin@97-126-1-93.tukw.qwest.net) | 22:53 | |
| ch | the rp2040 alarm sdk code seemed funny when i looked at it a while ago | 23:04 |
| + colinsane (~colinunin@97-113-95-212.tukw.qwest.net) | 23:06 | |
| - chomwitt (QUIT: Ping timeout: 264 seconds) (~alex@2a02:587:7a09:1500:42b0:76ff:fe46:a5fd) | 23:30 | |
| - reform13903 (QUIT: Remote host closed the connection) (~shard@2601:646:8f89:e680::563a) | 23:31 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!