2025-10-21.log

- kensanata (QUIT: Ping timeout: 244 seconds) (~alex@user/kensanata)00:05
+ kensanata (~alex@user/kensanata)00:06
+ paperManu (~paperManu@198.58.139.163)00:17
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)00:30
joschelb: wow this is really cool! I never saw a DIY pocket reform kit :D00:30
joschminute: might be of interest to you ^00:31
joschon fedi: https://social.sdf.org/@elb/11488945742498854600:38
joschelb: i found your comment about the charger board against the anodized aluminum frame interesting -- i haven't thought about that00:41
elbyeah I meant to bring that up at some point, but had forgotten until I processed that video00:41
elbI also had some comments about the assembly guide, I need to read it again00:41
elbit's very good, but ther eare one or two places where orientation wasn't entirely clear to me00:42
joschwe need the pdf of the assembly guide in git somewhere :)00:42
+ paperManu_ (~paperManu@198.58.139.163)00:42
elbit took me alomst exactly two months to process the footage from that video, maybe I'll do a usage impressions video by ... 2026 ;-)00:44
joschelb: and about your later comment about binary blobs -- there actually is a blob-free SoM for the reform: the LS1028A00:44
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)00:45
+ kensanata (~alex@user/kensanata)00:46
elbyeah, I was actually aware of that, but it's not really in the same class as the rockchip, unfortunately00:46
joschindeed00:47
elband someone is going to take me to task for the fact that Raspberry actually DOES design their own chips00:47
elbjust not the main SoC00:47
joschabout the slop of the cables: this actually already came in handy for the classic reform where a later addition of a display adapter was only possible because the display cable was "too long" for the original setup00:47
minuteelb: i skipped into your video earlier and coincidentally it was a point where you said something very interesting about solder mask being the only isolation under the charger board vs the aluminum. good point00:47
elbyeah it definitely avoids having to re-cable for upgrades/changes, and also allows for some floating usage during debugging or similar00:48
elbI thnk the only cable that really bugged me was the OLED cable00:49
elbbecause the offset it has in such a short cable seems like it's got to be torquing on the cable/connectors in an unfortunate way00:49
elbbut both the keyboard and the OLED display are tagged down pretty tight, so the lack of meaningful movement should help00:49
elbI love, love, LOVE how tight the keyboard is00:50
minuteelb: yeah the oled cable annoys me sometimes :D00:50
- violet (QUIT: Remote host closed the connection) (~vi@user/meow/violet)00:51
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)01:06
+ kensanata (~alex@user/kensanata)01:06
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)01:11
+ kensanata (~alex@user/kensanata)01:12
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)01:19
vkoskivI wrote about some linux debugging: https://vkoskiv.com/mesa-regression/01:21
vkoskivNot reform-related, but if there are factual mistakes in there, I think people here could spot those :D01:21
vkoskivI do have several reform-themed posts ideas on my list, but I only started collecting proper notes on things I worked on around ~202301:23
+ kensanata (~alex@user/kensanata)01:24
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)01:30
- paperManu_ (QUIT: Ping timeout: 264 seconds) (~paperManu@198.58.139.163)01:31
+ kensanata (~alex@user/kensanata)01:32
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)01:42
+ kensanata (~alex@user/kensanata)01:42
+ paperManu_ (~paperManu@198.58.139.163)01:51
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)01:56
+ kensanata (~alex@user/kensanata)01:56
- paperManu_ (QUIT: Ping timeout: 248 seconds) (~paperManu@198.58.139.163)01:58
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)02:13
+ kensanata (~alex@user/kensanata)02:14
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)02:19
+ kensanata (~alex@user/kensanata)02:21
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)02:26
+ kensanata (~alex@user/kensanata)02:26
- kensanata (QUIT: Ping timeout: 244 seconds) (~alex@user/kensanata)02:45
+ kensanata (~alex@user/kensanata)02:47
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)02:52
+ kensanata (~alex@user/kensanata)02:55
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)02:59
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)03:01
+ kensanata (~alex@user/kensanata)03:05
+ jogu (~jogu@user/jogu)03:05
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)03:09
+ kensanata (~alex@user/kensanata)03:10
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)03:15
+ kensanata (~alex@user/kensanata)03:16
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)03:21
+ kensanata (~alex@user/kensanata)03:23
- paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@198.58.139.163)03:36
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)03:45
+ kensanata (~alex@user/kensanata)03:45
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:06
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:09
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:09
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:09
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)04:32
+ kensanata (~alex@user/kensanata)04:32
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)04:46
elbit looks to me like there are a few global variables in pocket-hid/src/remote.c that either aren't used at all (alert_low_battery, alert_blink) or are effectively actually local (term_x, term_y); is there something I'm missing, are there plans for those, or are those things I can clean up?04:46
+ kensanata (~alex@user/kensanata)04:46
elbohhhhh I see, term_x and term_y aren't actually local, they're ... kind of dangerous04:49
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.6.130)05:05
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)05:13
+ Ar|stote|is (~linx@149.210.6.130)05:14
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)05:14
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)05:43
+ kensanata (~alex@user/kensanata)05:44
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)05:49
+ kensanata (~alex@user/kensanata)05:50
- jacqueline (QUIT: Ping timeout: 248 seconds) (~jacquelin@user/jacqueline)05:56
+ violet (~vi@user/meow/violet)05:56
+ jacqueline (~jacquelin@user/jacqueline)06:11
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)06:12
+ kensanata (~alex@user/kensanata)06:13
+ robin_ (~robin@user/terpri)06:36
- robin (QUIT: Remote host closed the connection) (~robin@user/terpri)06:36
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)06:41
+ kensanata (~alex@user/kensanata)06:41
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)06:44
+ kensanata (~alex@user/kensanata)06:44
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)06:50
+ kensanata (~alex@user/kensanata)06:51
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)06:56
+ kensanata (~alex@user/kensanata)06:57
- kensanata (QUIT: Ping timeout: 244 seconds) (~alex@user/kensanata)07:03
+ kensanata (~alex@user/kensanata)07:03
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)07:09
joschvkoskiv: thank you for that article. It's interesting that you bisect with the arch packaging around mesa and not just plain mesa git. But I had similar issues with meson config option mess during the bisect.07:12
+ kensanata (~alex@user/kensanata)07:13
joschvkoskiv: the reason i usually do not bisect the packaging is that the Debian packaging focusses around building *everything* and that makes each rebuild very slow and making the Debian build more minimal would be a lot of effort07:14
joschthe second reason why i use plain mesa git is because of how easy it is to run anything against mesa from git instead of mesa from my system07:14
joschfor example this was my last bisect recipe:07:15
joschmeson setup build -Dgallium-drivers="['panfrost']" -Dvulkan-drivers="[]" -Dplatforms="['x11','wayland']" -Dglx-direct=true -Dgbm=enabled -Dprefix=/home/josch/git/mesa/prefix --buildtype=debugoptimized && time meson compile -C build && meson install -C build07:15
joschand to run an application against that build i then run something like this:07:15
joschLD_LIBRARY_PATH=/home/josch/git/mesa/prefix/lib/aarch64-linux-gnu/ gajim07:15
joschthis is how i tracked down this bug in mesa in Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=111642707:18
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)07:18
joschturns out that was already known (and fixed) upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/1319107:19
+ kensanata (~alex@user/kensanata)07:19
joschthe fix is now backported and will be part of the next Debian stable update: https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/6207:21
+ FirefoxDeHuk (~FirefoxDe@109.108.69.106)07:30
+ shtrophic (~m-hrdsqi@user/shtrophic)07:33
- FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@109.108.69.106)07:35
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)07:39
+ kensanata (~alex@user/kensanata)07:39
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)07:47
+ kensanata (~alex@user/kensanata)07:48
+ FirefoxDeHuk (~FirefoxDe@109.108.69.106)08:05
- FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@109.108.69.106)08:09
- pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0)08:56
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)09:00
+ kensanata (~alex@user/kensanata)09:01
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)09:06
+ kensanata (~alex@user/kensanata)09:07
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)09:11
+ kensanata (~alex@user/kensanata)09:12
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)09:16
+ kensanata (~alex@user/kensanata)09:16
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)09:25
+ kensanata (~alex@user/kensanata)09:25
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)09:32
+ kensanata (~alex@user/kensanata)09:34
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)09:44
+ kensanata (~alex@user/kensanata)09:44
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)09:55
+ kensanata (~alex@user/kensanata)09:56
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)10:01
+ kensanata (~alex@user/kensanata)10:02
+ mjw (~mjw@gnu.wildebeest.org)10:11
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)10:13
+ kensanata (~alex@user/kensanata)10:14
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)10:40
+ kensanata (~alex@user/kensanata)10:40
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)10:45
+ kensanata (~alex@user/kensanata)10:45
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)11:01
+ kensanata (~alex@user/kensanata)11:02
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)11:06
+ kensanata (~alex@user/kensanata)11:10
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)11:29
+ kensanata (~alex@user/kensanata)11:29
+ FirefoxDeHuk (~FirefoxDe@109.108.69.106)11:35
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)11:42
+ kensanata (~alex@user/kensanata)11:42
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)11:46
+ kensanata (~alex@user/kensanata)11:47
- kensanata (QUIT: Ping timeout: 250 seconds) (~alex@user/kensanata)11:52
dormitofor the mnt reform pocket: what is the logic voltage level of the internal uart header? Is it module specific? I'm looking at the datasheet for the i.mx8m+, and it looks like it's uarts can operate in either 1.8v or 3.3v. I also am not seeing any thing about that on the SOM-carrier schematics.11:52
+ kensanata (~alex@user/kensanata)11:52
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)11:57
+ kensanata (~alex@user/kensanata)11:58
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)12:06
+ kensanata (~alex@user/kensanata)12:11
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)12:15
+ kensanata (~alex@user/kensanata)12:17
+ paperManu (~paperManu@198.58.139.163)12:20
- kensanata (QUIT: Ping timeout: 252 seconds) (~alex@user/kensanata)12:21
+ kensanata (~alex@user/kensanata)12:23
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)12:28
grimmwarevkoskiv: oh I read that recently and really appreciated it :)12:29
- FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@109.108.69.106)12:34
- mjw (QUIT: Killed (iridium.libera.chat (Nickname regained by services))) (~mjw@gnu.wildebeest.org)12:46
* Guest3333 -> mjw12:46
+ Guest7901 (~mjw@gnu.wildebeest.org)12:47
+ kensanata (~alex@user/kensanata)12:53
+ FirefoxDeHuk (~FirefoxDe@109.108.69.106)12:53
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)12:58
+ kensanata (~alex@user/kensanata)12:59
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)13:01
+ kensanata (~alex@user/kensanata)13:01
+ gustav25 (~gustav@c-78-82-53-228.bbcust.telenor.se)13:02
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)13:06
+ kensanata (~alex@user/kensanata)13:06
- kensanata (QUIT: Client Quit) (~alex@user/kensanata)13:11
+ kensanata (~alex@user/kensanata)13:11
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)13:15
+ kensanata (~alex@user/kensanata)13:20
+ erle (~erle@user/erle)13:27
- kensanata (QUIT: Ping timeout: 252 seconds) (~alex@user/kensanata)13:29
+ kensanata (~alex@user/kensanata)13:30
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)13:35
+ kensanata (~alex@user/kensanata)13:36
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)13:41
+ kensanata (~alex@user/kensanata)13:41
- kensanata (QUIT: Ping timeout: 244 seconds) (~alex@user/kensanata)13:46
+ kensanata (~alex@user/kensanata)13:47
- FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@109.108.69.106)13:47
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)13:52
bremnerjosch: if in doubt, blame gitlab13:54
bremner(re completion problems)13:56
+ kensanata (~alex@user/kensanata)13:57
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)14:01
+ kensanata (~alex@user/kensanata)14:03
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@198.58.139.163)14:05
- kensanata (QUIT: Ping timeout: 244 seconds) (~alex@user/kensanata)14:08
+ kensanata (~alex@user/kensanata)14:09
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)14:17
+ kensanata (~alex@user/kensanata)14:17
- buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org)14:23
+ buckket (~buckket@vps.buckket.org)14:24
- kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata)14:28
+ kensanata (~alex@user/kensanata)14:28
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)14:40
grimmwareminute: I've got a workaround for the display sleep issue15:04
grimmwareminute: https://source.mnt.re/grimmware/reform-debian-packages/-/commit/7b4a2f7c58b23dc9d076bb5b8a7c99c31e274fd1#eaf6e0dc1724268562cc82f38fff9d439f00aa41_668_66615:04
grimmwareignore the stuff about MIPI_DSI_MODE_LPM, that's just me reverting a previous test15:05
grimmwarebut basically if init works fine but enable doesn't then just do a full init :P15:05
grimmwarehence a workaround rather than a "fix" but it's kind of good enough15:05
grimmwarethe patch is weird because I'm directly editing the diff so I don't want to add or remove lines heh15:06
grimmwarebut essentially I'm booted into it now and it's working just fine15:06
grimmwarethis is based off fo your patch that fixes the flicker15:07
grimmwareand I've just found a workaround for the qutebrowser bug I was facing too :315:23
grimmwarea good day.15:23
+ pomel0 (~pomel0@user/pomel0)15:41
- plomtest (QUIT: Remote host closed the connection) (~plom@user/plomtest)15:56
+ plomtest (~plom@user/plomtest)15:57
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)16:16
+ qbit (~qbit@user/qbit)16:19
minutegrimmware: great16:33
minutegrimmware: good idea @ full init, i can patch that into my patch (basically just the ...init() line instead of ...power_on(), right? 16:34
- chomwitt (QUIT: Ping timeout: 245 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)16:39
grimmwareyeah, just init instead of display_on17:06
- Guest7901 (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org)17:43
minutegrimmware: hm, this looks like i should try init-in-enable in the dts for rk3588... i'll do that first17:52
minute(that workaround was for a311d initially)17:52
grimmwareyeah that sounds like a much simpler solution17:53
minutenot sure if it will just work though... 17:53
minutewell, i'll see in a few mins17:53
grimmwarereally glad I finally took the time to get my CI setup and reprepo going17:54
minutegrimmware: awesome yeah17:57
grimmwarejosch: just mailed you the tracking number for the imx8mp18:00
minuteaw, no more display for me18:06
grimmwareminute: is that with the init-in-enable?18:10
minutegrimmware: yeah, so it's not that simple. i'll try your change instead first 18:11
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-71-58.tukw.qwest.net)18:14
joschgrimmware: hype! \o/18:14
grimmwareminute: yeah looks like you'll be missing the MIPI_DSI_MODE_LPM and picking up some imx8mp-specific clock setting18:16
grimmwareotherwise the code is roughly functionally the same as my change18:16
+ colinsane (~colinunin@97-113-71-58.tukw.qwest.net)18:17
grimmwareif you want to reuse init-in-enable I think there's going to have to be something else in the device tree to indicate it's imx8mp18:17
grimmwareI know you were talking about refactoring this code, I think structuring it around the matrix of potential hardware combinations is probably a good idea18:19
grimmwareit means that as more modules come out or more screens have to be supported it becomes an additive thing18:20
erlejosch did you find time to try out my proposed patch for the fn neo2 thing?18:20
grimmwaremy gut feeling is that this is where DRY can become painful18:20
erlegrimmware DRY is not only about elegance and understanding, IMO it is mostly about maintenance. so if you never need to update something, then you are allowed to sin a little IMO ;)18:22
erleseriously offtopic, but my fav example for violating DRY is a magic card that has 3 lines of text and each of them says “target creature gets +1/+1.” … i have so far not found any way to make *that* DRY.18:25
erle(since you can choose the same target multiple times, you could give one creature +3/+3, or two creatures +2/+2 and +1/+1 respectively, or three creatures +1/+1 each. much more text if you try to DRY.)18:26
grimmwareI mean clarity trumps all other concerns in this space I feel :)18:28
erlei also thought about refactoring the handling of the fn keys for the keyboard stuff to prevent bugs like the one i encountered with the fn lock switching keys around, but then i thought: nope, it is already “good enough”, there is nothing to be gained if the hw revision is not even produced anymore.18:29
- pomel0 (QUIT: Ping timeout: 250 seconds) (~pomel0@user/pomel0)18:31
+ pomel0 (~pomel0@user/pomel0)18:32
* robin_ -> robin18:32
chdownloading artifacts for jobs/14554 now, then i'll see what the new kernel does18:40
grimmwarech: you're also v1 display right?18:41
chyeah18:41
grimmwaregood things coming :)18:42
minutegrimmware: you're right. my original plan was to make the driver as customizable as possible through dts so the quirks for each soc could be configured in the respective dts.18:43
minutebut sometimes worse is better... or at least ok for now18:43
minutenot saying your solution is "worse", i mean my current rube goldberg code in there18:43
grimmwareI get what you mean :)18:43
- erle (QUIT: Quit: K-lined) (~erle@user/erle)18:46
+ andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890e.rev.sfr.net)18:48
minutenow installing grimmware linux...18:48
grimmwaregrimmux18:48
minutedisplay is back on18:49
grimmware...18:51
+ rwa_ (~rene@2001:9e8:3388:8300:1d49:28f3:f844:247c)18:51
minutegrimmware: works!19:02
grimmwareEYYYYY19:02
minutegrimmware: good job! now how to make this releasable. 19:02
chminute: so the kernel from !140 cannot wake up my display19:12
minutegrimmware: i have a new theory. i think my patch just wasn't fully baked, and the 2nd init being required could explain it: mipi_dsi_dcs_exit_sleep_mode() is missing in the "wake up" path19:12
minutech: ok, that was kind of expected, good. my panel is just a bit different then than the one you and grimmware have.19:12
chthey are from different batches, right?19:13
minuteprobably19:13
- rwa_ (QUIT: Remote host closed the connection) (~rene@2001:9e8:3388:8300:1d49:28f3:f844:247c)19:20
grimmwareminute: what's incredibly frustrating is that that's what I was looking for (missing steps from enable) but because it's the *first* one I just wasn't seeing it19:34
+ Guest7901 (~mjw@gnu.wildebeest.org)19:34
grimmwarelike, I'm kind of astounded I missed that19:34
grimmwareminute: are you working on patching in the mipi_dsi_dcs_exit_sleep_mode()?19:37
grimmwaregoodness me the screen on this thing is very nice when it's not flickering19:38
minutegrimmware: yeah i'm trying that in the branch, just to see if my hunch was correct or not19:39
minutegrimmware: yes, non-flickering screen is much better :D19:39
grimmwarenice19:39
minuteok i should also try some other experiment now... driving displayport directly from rk358819:40
grimmwareI can test out your new branch tonight :) That is how I would like to spend my evening.19:40
minuteneat. let me see if it works for me first though, to save you some frustration :D19:41
grimmwarefair :)19:41
grimmwarereally optimistic about this charging board as well, it's been a good month for MNT19:41
minutenow testing https://source.mnt.re/reform/reform-debian-packages/-/jobs/14594/artifacts/browse/changes-arm64/20:06
minutegrimmware: yay!20:06
minutegrimmware: my patch doesn't work... funnily, the display backlight works though and it shows 1 line of colored pixel noise20:11
minutekind of like video stream is not turned on20:12
grimmwarehmm.20:13
minuteso yeah, maybe it just needs the full init (or some parts of it, but i think not worth it to dissect that now) after sleep+poweroff20:14
grimmwareyeah the re-init is so fast anyway20:14
elbI have questions about the keyboard firmware and style and development practices20:15
minuteon disp v1 it's kind of slow, but on v2 it's fast yeah20:15
elbI don't want to step on anyone's toes or make changes just for the sake of making changes, but there are some things I would change in here for just best embedded development practices, like removing unused variables, declaring (virtually all) globals static, etc.20:16
elbdoes that sound ... acceptable?20:16
elblike main.c and remote.c both have a fair number of global variables that are non-static but also not used in any other file, those are vulnerable to global variable unification problems in the future (but also many are namespaced, so ...)20:17
minuteelb: sounds good to me!20:24
minuteelb: meaning, these changes are welcome20:24
elbminute: awesome20:26
chlmk if there's a new kernel to test20:27
elbwould you rather one MR with a bunch of unrelated but mostly cleanup and simplfiication changes, or a number of smaller MRs with smaller and mostly-similar changes in each20:27
chpersonal opinion: for cleanups its nice to get MRs out more quickly because there's usually no need to group them or wait for anything20:30
minutech: just pushed a new version, pipeline will take a while of course. i did it like grimmware now but just removed the whole other branch in enable(). will need to test with imx8mp and dispv220:30
minuteelb: i agree with ch on that20:30
chbtw, 39C3 yay/nay?20:31
rick_if i may burst in here. i'm at 39c3 and bring my pocket reform with me <320:34
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)20:39
+ pomel0 (~pomel0@user/pomel0)20:44
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)20:48
minutech: yay!21:01
minuterick_: nice21:01
minutei just need to book hotel :021:01
minute(and be lucky to get a ticket of course)21:01
minutehmm, oops in panel_edp_probe+0x394/0x56821:02
chcool. yeah i also need everything still21:02
minuteah drivers/gpu/drm/panel/panel-edp.c:81421:02
minute(trying direct eDP from rk3588)21:02
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)21:03
minuteah lol21:03
minute> We're using non-optimized timings and want it really obvious that someone needs to add an entry to the table, so we'll do a WARN_ON splat.21:03
minute> panel-simple-dp-aux aux-fdec0000.edp: Unknown panel CMN 0x1239, using conservative timings21:03
minute0x1239 is chimei innolux, so aux seems to work21:03
minutesomething just crashes though, hmmm21:04
+ pomel0 (~pomel0@user/pomel0)21:04
- pomel0 (QUIT: Ping timeout: 252 seconds) (~pomel0@user/pomel0)21:09
- chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)21:10
minuteoh wow, got it to work (eDP)21:16
grimmware:O21:19
grimmwareFuckin TUESDAY YEAH.21:19
minutehaha21:20
minuteweird, the two desktop icons/illustrations in setup wizard are super mini smol on this system image21:22
cheDP on next, i assume?21:25
minutech: currently on classic (was easiest to test)21:25
joschi can confirm21:25
minutech: photo https://mastodon.social/@mntmn/11541377438721045221:25
minutejosch: mini small icons?21:25
joschyes21:26
minutejosch: i wonder what happened :0021:26
joschmaybe it was introduced as a result of some of the recent library bumps21:26
minutecould be21:27
grimmwareoh could it be a dpi scaling thing?21:28
joschi also wanted to share my recent usb-c contraption connected to my pocket reform: https://mister-muffin.de/p/c0sa.jpg -- took several USB-A to USB-C and vice-versa adapters to connect everything today21:32
joschthe last time my pocket rebooted was back in september, so before the recent firmware changes -- no problem since then21:33
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)21:33
joschi'm using it to take 1.5 hour lecture recordings and then encode the raw video on the pocket as well (no problems so far)21:33
sigrideven your adapter has an adapter21:33
joschthe pocket can now record video with such high quality that it is too much for a311d to play back XD21:34
minutejosch: wow ok :D21:37
chsomewhat surprising this doesnt run into a usb hub limit :D21:38
minute(meanwhile installing new kernel build on the pocket re:dispv1 flicker stuff)21:38
joschch: i'm surprised as well but i checked with lsusb because i had to make sure the camera got the 5 GiB/s for 1080p@60 MJPEG recording :)21:39
minutepocket display v1 on rk3588 works fine re:display off/on issues with this build https://source.mnt.re/reform/reform-debian-packages/-/jobs/14621/artifacts/browse/repo/pool/main/l/linux/21:42
minutenow i have to test with imx8mp...21:42
rick_oh regarding usbc stuff... should usbc dp alt mode work poket reform? dmesg always tells me 'maybe you have a bad cable?' i tried multiple usbc cables, docks and so one.. and nothing did work. it not that important for me, just asking if it should work xD21:42
chno21:43
rick_okay i see, so i don't need to debug it further. used mini hdmi after my tests, which works perfectly fine ^^21:44
minuterick_: there's no alt mode support in the current motherboard21:44
minutebut yeah, i also use microhdmi @ home with it 21:44
rick_yeah thats also enought for me. thanks for the info! :D21:45
chshould write down somewhere what the situation is on the rk. i forgot this like 3 times already21:46
minutetheoretically one could make a bizarro port board for pocket that splices into the charging stuff and muxes the eDP to another USB-C port21:49
minutebut i think i'd rather add some kind of alt-mode functionality to the motherboard later21:50
minutealso not sure how compatible the eDP is to DP21:50
chthe switchable pins are on the wrong port, was that it?21:50
minutech: yeah21:51
chmh21:51
minutei need to do a v2 pocket reform motherboard relatively soon though.......21:51
minutegrimmware: ok so with that double init patch, the display v1 still works on imx8mp21:58
grimmwareamazing.21:58
minutewill try dpms toggle on that machine...21:59
minuteuh oh22:00
grimmwareD:22:00
minutegrimmware: the flicker is back, on imx8mp :DD22:00
grimmwarewhat the fuck22:00
minutebut maybe...22:00
grimmwarethis is an emotional rollercoaster22:01
minutegrimmware: welcome to my job! lol22:01
elbch: minute: OK, well, then the first one is waiting :-)  !6722:03
minuteok so imx8mp dts has the "init-in-enable"22:03
minuteand only imx8mp has that22:04
minuteah well. it's clear why22:07
chthe watchdog reset on pocket-hid somehow seems to interfere with flashing 22:09
minutech: oh no22:09
* mjw -> Guest839222:09
- Guest8392 (QUIT: Killed (lead.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)22:09
* Guest7901 -> mjw22:09
minutech: isn't it turned off in the reset-for-flashing handler?22:10
+ Guest8392 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)22:10
chneed to checl22:11
- gustav25 (QUIT: Quit: Quit) (~gustav@c-78-82-53-228.bbcust.telenor.se)22:15
chi dont understand what HsvToRgb really does22:38
minutech: you mean _how_ it does what it does?22:38
chmostly i'm wondering if it aims to produce RGB in normal colorspace, or something else22:39
minutech: it aims to convert h/s/v to rgb 0-255 :D22:39
chhmm22:39
minutech: is there a problem with it?22:40
chso i wondered if i can stop hardcoding 0x004040 22:40
chwhich i assumed was in RGB22:40
minuteyeah that's rgb22:40
chbut converting that back using an online converter, i get some blue22:40
chnot pink22:40
minuteconverting that... back? to hsv?22:40
chhttps://www.colorhexa.com/00404022:41
minutech: ah sorry it's not RGB22:41
minutech: it's BGR or so22:41
minuteno22:41
minuteGRB?22:41
minuteok let me check :D22:42
ch400040 might match22:42
chso RBG?22:42
minutesomething is definitely odd22:43
minutevoid led_task(uint32_t color) {22:44
minute  uint32_t pixel_grb = color;22:44
minutelol22:44
minutei wonder if i had fixed that issue in keyboard422:44
minutech: i guess so far it didn't matter because there's no fixed value hsv input, just a wheel, so if it's out of phase one didn't notice22:45
chhttps://www.colorhexa.com/40004022:45
chi think color maybe, brightness no22:46
chso maybe more is going on22:46
minutech: well LED colors will look differently22:46
+ pomel0 (~pomel0@user/pomel0)22:46
chright22:46
chdo you know what the color was supposed to be in RGB?22:47
minutech: i cleaned up some of that stuff in keyboard4-fw, we should port that over22:47
minutech: well 0x400040 is correct. i think it was 0x800080 before and i halved the values, and it's swizzled because it's not really rgb in that codebase, but grb22:47
minutein reform-keyboard4-fw i think i untagled most of the rgb/hsv mess22:48
minuteand it also remembers the last chosen color22:48
minutech: https://source.mnt.re/reform/reform/-/blob/master/reform2-keyboard4-fw/src/leds.c?ref_type=heads22:48
chhttps://source.mnt.re/reform/pocket-reform/-/merge_requests/66 in the meantime this constrains power draw from the leds22:49
- schalken (QUIT: Ping timeout: 256 seconds) (~schalken@117-118-178-69.gci.net)22:49
- paperManu (QUIT: Ping timeout: 256 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)22:49
minutech: lgtm :D how did you come up with the threshold?22:49
+ schalken (~schalken@117-118-178-69.gci.net)22:50
chto my eyes at around that threshold there is a wide gap where the brightness does not -visibly- change until you go up to almost the meax22:50
chthe max22:50
minutech: oh nice22:50
chso that seemed good22:50
minutech: thanks, set to auto-merge22:51
chand i think lower than the threshold didnt change much power wise22:51
minutecool22:51
chhttps://source.mnt.re/reform/pocket-reform/-/merge_requests/67 from elb - i guess this needs a runner assigned?22:52
minutech: let me attempt a quick refactor of the leds stuff22:52
chk22:52
minuteoh yeah @ elb22:52
- pomel0 (QUIT: Ping timeout: 244 seconds) (~pomel0@user/pomel0)22:52
chi was gonna check out elb's MR and then the led color again22:52
minuteah no the runner is already there, probably just needs a rerun22:53
+ pomel0 (~pomel0@user/pomel0)22:57
chsway output power off/on works with the newest kernel build23:00
joschhehe, i have some reform-system-image changes but i see you are busy :D I'll push later to not hog the gitlab runner time :)23:01
minutech: nice. now i just need to fix that for imx8mp again ;/23:12
- schalken (QUIT: Ping timeout: 256 seconds) (~schalken@117-118-178-69.gci.net)23:12
+ schalken (~schalken@117-118-178-69.gci.net)23:14
grimmwarech: \o/23:20
minutech: yet untested https://source.mnt.re/reform/pocket-reform/-/merge_requests/6923:24
chseems sensible, gonna test23:26
- chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)23:28
chWFM23:30
chi think the min brightness on poweron could even be less23:32
minutenoice23:34
minuteit should be 0x200020 so... need to test that myself also :D23:35
chhttps://source.mnt.re/reform/pocket-reform/-/merge_requests/69/diffs#2260c41e482b89a87ab5c37958f1cfa1440397ba_117_120 23:36
chimo this can be < 0x623:36
minutech: ok, feel free to edit and i can test later! think i need to go home and get some rest23:37
minutebut nice session here today!23:37
chi dont think i can commit into your MR, but left a note23:38
chthe code changes all make sense to me23:38
minuteah, so i can merge first23:38
minuteah no, i created a conflict m)) ok tomorrow23:39
ch(:23:39
chget some rest23:39
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890e.rev.sfr.net)23:39
joschwas nice to read along :)23:40
- schalken (QUIT: Ping timeout: 244 seconds) (~schalken@117-118-178-69.gci.net)23:48
+ schalken (~schalken@117-118-178-69.gci.net)23:49
chhttps://source.mnt.re/reform/pocket-reform/-/merge_requests/65 also now tested and imo good23:52
chthe green led on the rcore carrier could also be less bright ;-)23:53
chjosch: you dont happen to have an esim module that can go into the sim card slot and can then be managed from linux?23:55
joschi would have to look up online what an "esim" is :D23:55
joschi have a normal sim card as far as i know23:56
chright23:58
chso normal sim cards will go away eventually23:58
chand instead you can download a sim profile ('esim') into a security chip your device already has23:58
chsome vendors figured out you can put that chip into a form factor where it looks like a normal simcard23:59
elbyeah I'd like all of the internal LEDs to be less bright23:59
elbthat's on my list of things to look at23:59
elblike if I can tell it's on _at all_ that's enough of my battery for an LED ;-)23:59
joschplease do this on your pocket reforms -- i need my classic reform as a torchlight at night!23:59
chblue+red leds on the right side should already be less bright than before23:59
elbI mean the classic reform has a clear bottom, that's fair ;-)23:59

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