| - ZylonMaster (QUIT: Quit: Leaving) (~fujwj@cpe-98-15-248-249.hvc.res.rr.com) | 00:07 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 00:08 | |
| + doctorhoo (~doctorhoo@2001:2043:5e0f:a800:d16:2bf7:ce8b:d9dc) | 00:09 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 00:21 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 00:24 | |
| - ephase (QUIT: Quit: WeeChat 4.0.5) (~ephase@2a01:e0a:2a:5300:f8d4:1fb6:b769:4362) | 00:32 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.32.15) | 01:00 | |
| + Ar|stote|is (~linx@149.210.32.15) | 01:01 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2001:2043:5e0f:a800:d16:2bf7:ce8b:d9dc) | 01:01 | |
| + doctorhoo (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 01:02 | |
| grimmware | not the best year for decisions. | 01:04 |
|---|---|---|
| - jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@utdpat241106.utdallas.edu) | 01:07 | |
| vkoskiv | lpc seems to be forgetting the charge state pretty regularly now - Seems like a regression, I didn't have this before | 01:08 |
| + jacobk (~quassel@utdpat242093.utdallas.edu) | 01:52 | |
| - jacobk (QUIT: Ping timeout: 272 seconds) (~quassel@utdpat242093.utdallas.edu) | 01:57 | |
| - unixpoet (QUIT: Ping timeout: 245 seconds) (~unixpoet@user/unixpoet) | 02:06 | |
| + unixpoet (~unixpoet@user/unixpoet) | 02:08 | |
| - unixpoet (QUIT: Ping timeout: 240 seconds) (~unixpoet@user/unixpoet) | 02:12 | |
| abortretryfail | vkoskiv: mine was like that, consistently bad until a deep-discharge event and it's been rock-solid since | 02:13 |
| abortretryfail | one side note: My LPC is running a patched firmware that disables the brown-out detection | 02:13 |
| abortretryfail | I wonder if the same sort of "cold boot" might work if you disconnect the batteries for a while | 02:14 |
| violet | thinking of falling down the rabbit hole and trying to get linux-rt working | 02:50 |
| - mjw (QUIT: Ping timeout: 255 seconds) (~mjw@77-174-248-71.fixed.kpn.net) | 04:50 | |
| + unixpoet (~unixpoet@user/unixpoet) | 05:54 | |
| josch | violet: would setting preempt=full give you enough realtime capabilities? | 06:49 |
| violet | it'd probably help but the rt patchset still isnt fully merged from my understanding | 07:41 |
| violet | how much i actually need.. well im kinda exploring that to find out! | 07:41 |
| violet | my end goal is to be able to do low-jitter low-latency midi sequencing of hardware | 07:41 |
| violet | low-jitter being the harder part of those | 07:42 |
| violet | particularly on linux | 07:42 |
| violet | (ill prolly have to mod the software i want to use so that the midi stuff is handled differently and maybe make it use https://github.com/thestk/rtmidi ) | 07:43 |
| violet | with some other stuff though like im basically exploring the whole space of real time audio on linux for the first time | 07:44 |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-113-128-229.tukw.qwest.net) | 07:49 | |
| + colinsane (~colinunin@97-113-128-229.tukw.qwest.net) | 07:49 | |
| - pandora (QUIT: Quit: Connection closed for inactivity) (uid585533@id-585533.ilkley.irccloud.com) | 08:38 | |
| - Boostisbetter (QUIT: Ping timeout: 240 seconds) (4a410829d7@irc.cheogram.com) | 12:34 | |
| + mjw (~mjw@77-174-248-71.fixed.kpn.net) | 12:38 | |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@77-174-248-71.fixed.kpn.net) | 12:53 | |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-113-128-229.tukw.qwest.net) | 14:02 | |
| + colinsane (~colinunin@97-113-128-229.tukw.qwest.net) | 14:04 | |
| + RFIDtag (~RFIDtag@31.207.58.205) | 14:24 | |
| - doctorhoo (QUIT: Ping timeout: 255 seconds) (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 14:25 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 14:26 | |
| + doctorhoo (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 14:27 | |
| + jacobk (~quassel@64.189.201.150) | 14:34 | |
| - RFIDtag (QUIT: Quit: leaving) (~RFIDtag@31.207.58.205) | 14:42 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@64.189.201.150) | 15:10 | |
| + jacobk (~quassel@64.189.201.150) | 15:42 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 17:12 | |
| + doctorhoo (~doctorhoo@2001:2043:5e0f:a800:b53e:e740:1578:96ed) | 17:12 | |
| - doctorhoo (QUIT: Ping timeout: 258 seconds) (~doctorhoo@2001:2043:5e0f:a800:b53e:e740:1578:96ed) | 17:21 | |
| + doctorhoo (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 17:22 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 17:30 | |
| + doctorhoo (~doctorhoo@2001:2043:5e0f:a800:e0e2:1bbc:e241:2462) | 17:30 | |
| - doctorhoo (QUIT: Ping timeout: 252 seconds) (~doctorhoo@2001:2043:5e0f:a800:e0e2:1bbc:e241:2462) | 17:35 | |
| + doctorhoo (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 17:35 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 17:40 | |
| + doctorhoo (~doctorhoo@2001:2043:5e0f:a800:1b2b:5008:b860:99fc) | 17:40 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@64.189.201.150) | 17:54 | |
| + mjw (~mjw@89.205.143.198) | 17:55 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2001:2043:5e0f:a800:1b2b:5008:b860:99fc) | 17:59 | |
| + doctorhoo (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 17:59 | |
| - mjw (QUIT: Remote host closed the connection) (~mjw@89.205.143.198) | 18:19 | |
| + mjw (~mjw@89.205.140.82) | 18:29 | |
| - mjw (QUIT: Remote host closed the connection) (~mjw@89.205.140.82) | 18:40 | |
| + mjw (~mjw@89.205.140.82) | 18:40 | |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@89.205.140.82) | 18:55 | |
| + mjw (~mjw@89.205.129.242) | 18:55 | |
| - mjw (QUIT: Ping timeout: 260 seconds) (~mjw@89.205.129.242) | 19:00 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 19:55 | |
| vkoskiv | I looked into the forgetful LPC/brownout thing a bit, 76e4ff in April enabled the already existing brownout_setup() for all mb revisions, so it's possible that the regression I experienced since flashing LPC a few weeks ago is indeed that | 20:20 |
| vkoskiv | Looking at the docs, we're currently setting the threshold to level 3, meaning the interrupt threshold is 2.63V, and the de-assert threshold is 2.71V | 20:21 |
| vkoskiv | The next step down would be interrupt 2.35V, de-assert 2.43V | 20:22 |
| vkoskiv | Which seems a little low, as LiFePO4 shouldn't go much below 2.5V, and 2.35V is pretty solidly below that. | 20:22 |
| vkoskiv | But my LPC seems to forget the capacity when we're nowhere near those voltages, usually it happens soon after unplugging at 100% | 20:22 |
| vkoskiv | So I'm still well over 3V on all cells, I'd think. | 20:23 |
| minute | vkoskiv: it's not about lifepo voltage. it's about the 3v3 standby voltage. | 20:52 |
| minute | i.e. if 3v3 standby voltage dips for a moment (not sure when/why), it would brownout | 20:57 |
| vkoskiv | Ahh, okay. In that case the level 3 makes much more sense | 21:11 |
| minute | yeah, but maybe it's noisy | 21:13 |
| minute | so it's a good idea to try to set it as low as possible | 21:13 |
| + mjw (~mjw@gnu.wildebeest.org) | 21:33 | |
| vkoskiv | Of course now that I'm testing it, it doesn't forget the harge level :D | 22:39 |
| josch | minute: if you like, i have another large-ish MR to review: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/20 | 23:10 |
| josch | with this merged, you now no longer have to create a new branch to build linux from experimental, for example | 23:10 |
| josch | you can just choose a different BASESUITE when running the pipeline manually | 23:10 |
| josch | it looks like this: https://mister-muffin.de/p/on1w.png | 23:10 |
| minute | josch: awesome! will do some reviews tomorrow | 23:14 |
| josch | minute: cool! would you like me to get your firedecor fork into debian? | 23:16 |
| minute | josch: that would be pretty great actually | 23:16 |
| josch | wayfire 0.8.0 is already packaged and uploaded in experimental | 23:17 |
| josch | should i call it firedecor or reform-firedecor? | 23:17 |
| minute | josch: i removed quite some features from firedecor and will further clean up the code, so reform-firedecor would be best | 23:17 |
| josch | minute: it would be handy to have a release tag on https://github.com/mntmn/Firedecor | 23:27 |
| josch | minute: please ping me once you added a tag. Once that exists, I'll submit the ITP. | 23:35 |
| minute | josch: alright, it's in my todo now! | 23:36 |
| josch | cool :) | 23:36 |
| Boostisbetter | man, I am loving how stable standby is on the Reform these days. It is super impressive how much progress the polish on the Reform has gotten. Things just are working super well these days! | 23:38 |
| josch | Boostisbetter: good news for you then: kernel 6.5 is now in stable-backports. So if you like, you can soon get Debian stable *and* standby. :) | 23:39 |
| Boostisbetter | josch: woot! | 23:41 |
| Boostisbetter | Stable is my jam! | 23:41 |
| josch | i already ported reform-debian-packages (see MR above) and reform-system-image to sysimage-v4 and just need to fix the html some time next week to offer the stuff that is now built | 23:45 |
| josch | once that is done, reform.d.n will offer system images, packages and debian-installer not only for imx8mq but also for a311d and ls1028a | 23:47 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
