2025-12-26.log

minutethanks! see you there! :D00:00
- bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@134.22.115.162)01:38
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)02:54
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156)03:27
+ paperManu (~paperManu@146.71.9.156)03:34
- rodion_goritskov (QUIT: Ping timeout: 240 seconds) (~rodion_go@mail.goritskov.com)04:44
- paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@146.71.9.156)05:10
- spew (QUIT: Quit: nyaa~) (~spew@user/spew)06:05
+ pomel0 (~pomel0@user/pomel0)06:52
- manis (QUIT: Ping timeout: 256 seconds) (01a66df340@185.72.67.185)07:45
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)08:18
+ pomel0 (~pomel0@user/pomel0)08:43
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)08:50
+ pomel0 (~pomel0@user/pomel0)08:55
+ manis (01a66df340@185.72.67.185)09:27
+ libercv (~libercv@user/libercv)09:29
- kensanata (QUIT: Quit: OK) (~alex@user/kensanata)09:48
+ kensanata (~alex@user/kensanata)09:48
- nybble (QUIT: Quit: WeeChat 4.8.1) (~sprang@user/csprng)10:33
- libercv (QUIT: Quit: Konversation terminated!) (~libercv@user/libercv)10:46
grimmwareminute: I'm still having issues with battery balancing sometimes when the pocket gets drained. One cell will be a lot higher voltage than the other and then the sysctl struggles to continue to deliver an appropriate voltage to actually charge either cell12:06
grimmwaremy observation here is that with the charger board v2 it will *eventually* recover but I don't understand how it's managing to get such a discrepency in the first place, surely the draw should be even across the cells?12:08
grimmwareI'm on the last commit for sysctl firmware12:09
grimmwareAt some point in the new year I'd love to have a chat about this so that I can understand what I can do to try to debug the issue12:09
minutegrimmware: yeah that sounds weird12:10
minutegrimmware: you're not at 39c3 i guess?12:10
grimmwarenah12:10
grimmwarewhich is sad because I'd really love to say hi irl at some point :)12:11
minutegrimmware: i think we should configure the max chip properly. by setting the right values in that windows app. so the protection works correctly. maybe it interferes somehow12:11
minutegrimmware: yeah would be cool to hang!12:11
grimmwareare you planning on EMFcamp next year in the UK?12:12
grimmwareack on the max chip, I've got a Windows PC set up at the moment if you can give me some notes on what you were thinking about doing12:13
minutenope @ camp12:16
minutejosch: btw i can confirm my current kernel 6.17.13 job results in a working rk3588/pocket reform kernel incl hdmi 1440p@120hz still working.12:17
joschwow, that's a lot of pixels per second o012:19
joschthank you for confirming -- i can barely test hdmi stuff here :D12:20
minutegrimmware: https://minute.social/secret-room/MAXREFDES179_Battery_Fuel_Gauge_GUISetup1.0.0.zip12:20
joschand fewer patches will make it easier to forward-port the remainder next time12:21
joschminute: I'll remove 67, 67 and 68 from the 6.18 branch too, okay?12:22
joschthe reason i left them in was because their description sounded suspend-related and i wanted to make playing around this this easier for folks but i remember you wanted to do another deep-dive into this topic anyway "soon"12:23
minutegrimmware: this has a wizard where you have to enter the min and max values and general parameters for the cells and at the end it generates (even graphically, like a diff) the config registers that need poking12:24
minutegrimmware: i can't find any manual for that tool but iirc it is complex, but mostly self explanatory. some values might need best guesses or you need to do a bit of web research.12:25
minutejosch: yes, i thought i had already merged that removal into that branch but please go ahead12:25
joschminute: oh shoot wait there is a typo in the commit message! You removed 76, 77 and 78 not 66, 67, 68 as it says in the commit message12:28
joschokay, now it makes much more sense that you said that hdmi 1440p@120hz still works because 66, 67, 68 do not seem to be very much hdmi related XD12:29
minuteoh?12:29
minutei'll quickly check12:30
minutejosch: can you later als merge this into that branch? :D https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/15412:30
minutejosch: you're right, i thought you meant other patches, sorry @ 6712:31
minutejosch: i thought you meant 76,77,7812:31
minutewhich iirc are hdmi related and upstreamed12:31
joschyes, the confusion is solved. 0076, 0077 and 0078 were removed by vimja. Now it makes sense that you thought this was already done for 6.18. It is. :)12:35
joschI merged MR154 into 6.18 now as well.12:35
joschi'm going to push that branch into the "josch" namespace as well and do a build with DIST=experimental and then create another system image from that12:41
joschi'm currently on Pocket Reform LTE internet in a regio without wifi, so lets see when I get a chance to download that system image during the day. :)12:41
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@46-144-38-170.biz.kpn.net)12:58
minutejosch: wow nice :D13:13
minutejosch: i got the numbers confused last night and mislabeled this commit (it's actually about 76/77/78) https://source.mnt.re/reform/reform-debian-packages/-/commit/665b72bd905150d8ddf43a14a5ea6836e117659013:15
joschminute: yes, i thought that's what we had discovered earlier?13:15
minutejosch: yes, but i didn't remember that i also got it wrong in that commit title :D13:34
minutejosch: ah now i see that you knew that :D13:34
minutejosch: sorry, a bit in a rush because of 39c9 prep and glancing over things13:35
minutebut i finally have my own reform-system-image fork!13:35
minute(i hope to boot this on qcs8550 later, which i will also take with me) https://source.mnt.re/mntmn/reform-system-image/-/jobs/1690813:35
+ amospall1 (~jordi@user/amospalla)13:35
- amospalla (QUIT: Ping timeout: 256 seconds) (~jordi@user/amospalla)13:38
joschminute: all good, all good! I'm just glad that I cared to check and did not accidentally remove the wrong patches. No harm done! I hope it boots on qcs8550 :)13:41
joschah drats i should've taken my rk3588 classic reform with me, then we could've extended this post with data from qcs8550: https://community.mnt.re/t/comparing-battery-runtime-of-rk3588-a311d-i-mx8mq-i-mx8m-and-ls1028a/391713:42
josch(maybe :D)13:43
+ paperManu (~paperManu@146.71.9.156)14:02
cliHi, offtopic question: which 3D printer aligns most to open hardware principles? Prusa? Sorry if this is not the right place to ask. Though I am 100% sure that some folk here know lots about one and the other :)14:46
+ spew (~spew@user/spew)15:05
gordon1cli: voron16:22
gordon1but prusa is open too, however prusa slicer recently has been enshittifed with some web browser bs16:23
gordon1but yeah, kinda offtopic16:23
+ RandyK_ (~RandyK@user/randyk)16:40
- RandyK (QUIT: Quit: Disconnecting. Probably for some good reason.) (~RandyK@user/randyk)16:41
* RandyK_ -> RandyK16:41
+ paperManu_ (~paperManu@146.71.9.156)17:06
cliThanks :)17:13
grimmwareminute: ah I get you17:23
grimmwareyeah I can probably take a look at that17:23
gordon1cli: if you decide to go with voron ldo kit, pls lurk the internet for caveats, it is not 100% smooth and straightforward experience as people might make you to believe17:24
- paperManu_ (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156)17:25
+ murphnj (~murph@user/murphnj)17:54
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)19:05
+ pomel0 (~pomel0@user/pomel0)19:05
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)19:11
+ qbit (~qbit@user/qbit)19:12
- pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0)19:21
+ pomel0 (~pomel0@user/pomel0)19:21
+ mjw (~mjw@46-144-38-170.biz.kpn.net)19:31
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)20:11
f_lol I was just about to ask about battery runtime20:17
joschf_: of what?20:18
f_reform SoM's20:19
joschah well, there you go i guess :)20:19
f_btw, on "So you look at A311D and you like how long it makes your laptop last but then you realize that the video you want to watch with your bluetooth headphones is encoded in 60fps 1080p for which A311D is too slow to decode" -- A311D is actually supposed to be able to watch 4k60 without trouble20:19
joschf_: but these are of course not realistic at all but the stuff that goes on top of these numbers will be about the same for each som20:19
f_but the vdec drivers story is .. something20:19
joschf_: does it work in mainline or not? :)20:20
f_kinda but also kinda no20:20
joschi recently got 4k@60 h264 hardware decoded on rk3588 :)20:20
joschhad to patch ffmpeg and mpv but it works!20:20
f_there's a driver around for A311D vdec20:20
f_but uhh20:20
f_it's still in staging and is mostly unfinished, also requires a patched ffmpeg to work at all, and you can basically forget about 10-bit 4k media20:21
f_I hope this won't be the case for much longer though20:21
f_https://lore.kernel.org/all/20251124-b4-s4-vdec-upstream-v2-0-bdbbce3f11a6@amlogic.com/20:22
joschoh no don't link me patches i might get tempted XD20:22
f_josch: oh don't worry the patch series doesn't compile20:22
f_xD20:22
f_or at least v1 didn't20:23
joschwhat a relief :)20:23
f_as can be seen by robher and krzk literally yelling at them20:23
f_heh20:23
f_but that's kind of my last hope at vdec support20:24
f_Also, regarding > Then you’d like to suspend your system. Sorry, neither A311D nor RK3588 can do that.20:24
f_A311D ..... does have the ability to suspend20:24
joschokay, sorry20:24
joschi meant suspend *and* resume :)20:24
f_does it not work on reform rn?20:25
f_yeah suspend and resume it should do just fine.20:25
joschwhut?20:25
f_Oh now I see the problem20:25
f_this stupid SCP firmware that is bl30 has no idea what the reform keyboard is20:25
f_so you can suspend but not resume :P20:25
joschah yes20:25
f_maybe you can resume by sending stuff over UART to wake it up20:26
f_thankfully the resume part is customisable in bl301 iirc20:26
joschdo i hear somebody volunteer? :)20:26
f_I don't yet have a reform :p20:27
joschwould you do it if you had?20:27
joschthings can be arranged20:27
f_maybe, but also I'm currently just waiting for the reform next to get one20:28
f_which I will pay20:28
f_:)20:28
joschrk3588 is quite nice too20:28
f_and I'm planning to get rk3588 and not a311d20:29
joschbut i still didn't switch because i am so happy with a311d20:29
f_However I do have a BPI-CM4 minute sent me a while ago20:29
+ qbit (~qbit@user/qbit)20:29
f_so in theory all I'd need would be the RCM4 board thing when I get it20:29
joschf_: i can also borrow you a reform motherboard if that would help you20:29
f_thanks but hopefully the reform next will work when it comes out :)20:31
joschfingers crossed!20:31
f_not sure how different it is from the OG reform, like board-wise20:31
joschthe keyboard attached to the next is the same as in classic reform20:32
f_I do prefer its looks much more than the OG, the OG is much thicker than my current 2011 laptop which is already pretty thick ;)20:32
f_(but I do otherwise like the OG's look too!)20:32
joschthe look on people's face it when i turn it upside down to have them see the transparent bottom is worth everything for me :)20:33
f_haha yes :D20:33
f_Huge props on that!20:33
joschokay, train is arriving -- ttyl20:33
f_\o20:33
f_this is how librecomputer does it to wake on uart https://github.com/libre-computer-project/libretech-amlogic-boot/commit/04b4018539e83188783aee5557154a10cc15f1d120:36
f_fwiw20:36
plomlompomSo ... I'm sitting at the MNT assembly now @ 39c3.22:08
plomlompomTurns out it's much easier to find by using the map from the current year rather than my c3nav's map from last year.22:09
- pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0)22:54
+ pomel0 (~pomel0@user/pomel0)22:54
+ bkeys (~Thunderbi@172.13.200.151)23:13
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@46-144-38-170.biz.kpn.net)23:50

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!