| - chomwitt (QUIT: Ping timeout: 255 seconds) (~chomwitt@2a02:587:7a0a:c00:1ac0:4dff:fedb:a3f1) | 00:18 | |
| - S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin) | 00:31 | |
| - iank (QUIT: *.net *.split) (~iank@fsf/staff/iank) | 00:33 | |
| - _nrb_ (QUIT: *.net *.split) (~nrbnrb@xmpp01.you-host.me) | 00:33 | |
| - leonardo (QUIT: *.net *.split) (~leonardo@user/leonardo) | 00:33 | |
| - spiral (QUIT: *.net *.split) (~spiral@198.98.57.6) | 00:33 | |
| + iank (~iank@fsf/staff/iank) | 00:33 | |
| + _nrb_ (~nrbnrb@xmpp01.you-host.me) | 00:33 | |
| + leonardo (~leonardo@user/leonardo) | 00:34 | |
| + S0rin (~S0rin@user/s0rin) | 00:34 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 00:38 | |
| - S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin) | 00:40 | |
| + S0rin (~S0rin@user/s0rin) | 00:40 | |
| vagrantc | is it expected that the battery status gets reset after the LPC firmware upgrade? it was at 100% before the flash, and now at ???% ... | 00:47 |
|---|---|---|
| vagrantc | interestingly, with the reform-lpc-dkms module loaded, the interface in /sys/class/power/... shows ~90% (which would be reasonable for a bit of runtime without external power | 00:47 |
| vagrantc | don't know how it is all attached, but would seem odd that one interface can read the remaining capacity while the other couldn't, though maybe there are two different strategies to guess that? | 00:48 |
| kfx | iirc the kernel side has 1800mAh batteries hardcoded, while the LPC tries to infer capacity from behavior | 00:49 |
| kfx | don't quote me, I'm probably wrong! | 00:49 |
| vagrantc | ah, well, i'm still using the cells i got with it ... so i think 1800mAh is theoretically correct... | 00:55 |
| vagrantc | definitely have doubts about at least one of the cells, which had a spurious drop to 2.2v while all the other cells were ~3.1 | 00:56 |
| vagrantc | low enough to hard power off at an awkward moment :/ | 00:57 |
| vagrantc | but it's all better now. maybe. | 00:57 |
| kfx | my absolute favorite thing about the reform is I can just shove more batteries in because I feel like it | 00:57 |
| kfx | I don't have to order some $1200 OEM replacement or trust some ebay refurb grenade | 00:58 |
| - S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 00:58 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-4-79.mobile.nym.cosmote.net) | 01:00 | |
| + Ar|stote|is (~linx@149-210-4-79.mobile.nym.cosmote.net) | 01:00 | |
| + S0rin (~S0rin@user/s0rin) | 01:02 | |
| - mtm- (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 01:03 | |
| sigrid | vagrantc: that is expected after upgrade since the prior "learnings" of the batteries get wiped on reset of lpc | 01:06 |
| sigrid | fw could be changed to make it possible to tell it (from the OS) what capacity batteries actually have | 01:07 |
| sigrid | likewise, the current "state" could be stored in eeprom, i believe, so they would not get wiped on reset | 01:08 |
| sigrid | but that is not implemented | 01:08 |
| sigrid | (patches welcome) :) | 01:08 |
| vagrantc | of course, just checking in if it's known behavior and whatnot :) | 01:11 |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:20 | |
| - S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 01:23 | |
| + S0rin (~S0rin@user/s0rin) | 01:38 | |
| + vagrantcc (~vagrant@97-120-35-211.ptld.qwest.net) | 02:25 | |
| - vagrantcc (QUIT: Quit: leaving) (~vagrant@97-120-35-211.ptld.qwest.net) | 02:35 | |
| + vagrantcc (~vagrant@97-120-35-211.ptld.qwest.net) | 02:37 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:10 | |
| - mtm (QUIT: Remote host closed the connection) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:20 | |
| - bluerise (QUIT: Ping timeout: 255 seconds) (~bluerise@user/bluerise) | 03:21 | |
| + bluerise_ (~bluerise@p5b211556.dip0.t-ipconnect.de) | 03:21 | |
| vagrantcc | rewrote my keyboard firmware with a few small changes to the layout which fits my needs much better ... only unresolved issue appears to be a bigger right shift | 03:48 |
| vagrantcc | heh. didn't even notice the DEL key | 03:48 |
| vagrantcc | basically swapped the compose an ctrl key, made hyper a control, put alt keys on the outside of the space bars, and put pgup/pgdn in the middle of the space bar ... and hyper where pgdn used to be... | 03:50 |
| + chartreuse (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net) | 03:58 | |
| - S0rin (QUIT: Ping timeout: 240 seconds) (~S0rin@user/s0rin) | 04:04 | |
| + S0rin (~S0rin@user/s0rin) | 04:08 | |
| vagrantcc | maybe need to move compose somewhere else, and just make it another ctrl | 04:27 |
| kfx | vagrantcc: I put a ridged keycap on right shift so I wouldn't miss it any more | 04:36 |
| kfx | http://sciops.net/information/technology/reform_school/keyboard/homing_shift.jpg | 04:36 |
| vagrantcc | sounds plausibly workable | 04:43 |
| vagrantcc | thanks | 04:46 |
| vagrantcc | ACTION wave | 04:46 |
| vagrantcc | s | 04:46 |
| - vagrantcc (QUIT: Quit: leaving) (~vagrant@97-120-35-211.ptld.qwest.net) | 04:46 | |
| - S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin) | 05:04 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 05:25 | |
| + S0rin (~S0rin@user/s0rin) | 06:08 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 06:32 | |
| - TadeusTaD (QUIT: *.net *.split) (tadeustad@psifactor.pl) | 06:57 | |
| - XgF (QUIT: *.net *.split) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 06:57 | |
| - Asmadeus (QUIT: *.net *.split) (~asmadeus@240b:13:8c80:d300:e:98c:8000:d300) | 06:57 | |
| - rah (QUIT: *.net *.split) (rah@verain.settrans.net) | 06:57 | |
| - Kooda (QUIT: *.net *.split) (~kooda@natsu.upyum.com) | 06:57 | |
| + rah (rah@verain.settrans.net) | 06:57 | |
| + TadeusTaD (tadeustad@psifactor.pl) | 06:57 | |
| + Asmadeus (~asmadeus@240b:13:8c80:d300:e:98c:8000:d300) | 06:57 | |
| + XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 06:57 | |
| + Kooda (~kooda@natsu.upyum.com) | 06:57 | |
| - S0rin (QUIT: Ping timeout: 240 seconds) (~S0rin@user/s0rin) | 07:27 | |
| + S0rin (~S0rin@user/s0rin) | 07:33 | |
| + chomwitt (~chomwitt@2a02:587:7a0a:c00:1ac0:4dff:fedb:a3f1) | 08:39 | |
| - kklimonda (QUIT: Read error: Software caused connection abort) (sid72883@user/kklimonda) | 10:37 | |
| + kklimonda (sid72883@user/kklimonda) | 10:37 | |
| - chomwitt (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:587:7a0a:c00:1ac0:4dff:fedb:a3f1) | 10:52 | |
| - buckket (QUIT: Remote host closed the connection) (~buckket@pdp8.buckket.org) | 11:32 | |
| + buckket (~buckket@pdp8.buckket.org) | 11:36 | |
| - hl (QUIT: Read error: Software caused connection abort) (~hl@user/hl) | 11:42 | |
| + hl (~hl@user/hl) | 11:42 | |
| - hl (QUIT: Quit: ZNC - https://znc.in) (~hl@user/hl) | 11:59 | |
| + hl (~hl@user/hl) | 12:01 | |
| + chomwitt (~chomwitt@athedsl-351939.home.otenet.gr) | 12:01 | |
| * bluerise_ -> bluerise | 15:23 | |
| - bluerise (QUIT: Changing host) (~bluerise@p5b211556.dip0.t-ipconnect.de) | 15:23 | |
| + bluerise (~bluerise@user/bluerise) | 15:23 | |
| + bgs (~bgs@212-85-160-171.dynamic.telemach.net) | 16:22 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 18:06 | |
| - chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@athedsl-351939.home.otenet.gr) | 19:50 | |
| josch | so.... updating the firmware was very easy and straight forward. Nice! | 20:03 |
| josch | I switched some of my keys around which was also very easy. | 20:04 |
| vagrantc | ACTION too | 20:04 |
| josch | What is not so nice is, that a) there are no git tags for the firmware b) there is no changelog with important changes for each new version c) the version displayed in the oled is quite meaningless -- it's stuck at february this year | 20:05 |
| vagrantc | josch: i've got some rough packaging here: https://salsa.debian.org/vagrant/mnt-reform-firmware | 20:06 |
| josch | reading the "git log" output it seems that pressing circle and 1 is not supposed to switch the som off and on again if it's already on? this doesn't work for me, my reform still turns off and on again. do i need to update lpc as well? | 20:06 |
| vagrantc | would really like to see the firmware repository separated from all the other stuff | 20:07 |
| josch | vagrantc: hah, now i know how you probably found out how it's reproducible :) | 20:07 |
| vagrantc | josch: yeah, easiest way to check for reproducibility is package it and run reprotest on it :) | 20:07 |
| josch | vagrantc: yes, i think that would make its development and tracking of changes much easier | 20:07 |
| vagrantc | ideally one repository for firmware... they don't seem to share much, if any code | 20:08 |
| vagrantc | needs a bit more work before uploading to debian... | 20:09 |
| vagrantc | there are a bunch of windows binaries in there, presumably not compiled from source | 20:09 |
| vagrantc | i managed to git bit-for-bit reproducible results when i purged them, so obviously not in the parts i care about | 20:10 |
| vagrantc | dunno if i should make a separate repository and use some sort of git filter to rebase it or what... currently i'm just "git rm"ing files that aren't needed | 20:11 |
| vagrantc | or a separate repository for each of the keyboard, trackball, trackpad, lpc ... | 20:14 |
| vagrantc | josch: regardless of weather it needs the lpc firmware ... there are some nice improvements in there | 20:16 |
| vagrantc | josch: so i'd recommend upgrading | 20:16 |
| josch | vagrantc: yes, it's upgraded. :) | 20:26 |
| josch | vagrantc: the question how to package it is probably solved once there is some decision on how to continue development on the firmware packages. | 20:26 |
| josch | if there are no git tags then maybe at least the KBD_FW_REV define from constants.h could be generated from the latest git commit hash when running make? That would give a much clearer indication what firmware one is currently running. | 20:32 |
| vagrantc | there's also apparently FW_REV for the lpc firmware ... don't see anything similar for track* | 22:03 |
| + chomwitt (~chomwitt@athedsl-351939.home.otenet.gr) | 22:03 | |
| vagrantc | the "proper" thing to do, would be one source package per firmware ... but the lazy thing would be to lump them all together | 22:03 |
| - bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net) | 22:08 | |
| josch | yup | 22:20 |
| vagrantc | i think i'd have to do KBD_FW_REV/FW_REV+N.$githash or something, since clearly we want all the shiny new things :) | 22:21 |
| vagrantc | with most projects lately, I use a git describe to get N and $githash, but without tags, git describe doesn't work so well | 22:22 |
| josch | fatal: No names found, cannot describe anything. | 22:31 |
| vagrantc | exactly | 22:32 |
| josch | first time i've seen that message XD | 22:33 |
| - chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@athedsl-351939.home.otenet.gr) | 23:49 | |
| vagrantc | josch: https://source.mnt.re/reform/reform-debian-packages/-/blob/main/linux/config is just the modules not included in the debian kernel yet? | 23:58 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
