| - mjw (QUIT: Ping timeout: 272 seconds) (~mjw@66.183.205.74) | 00:17 | |
| + oliverD (~Thunderbi@user/oliverd) | 00:28 | |
| - oliverD (QUIT: Remote host closed the connection) (~Thunderbi@user/oliverd) | 00:31 | |
| - AnimaInvicta (PART: !!unknown attribute: msg!!) (~AnimaInvi@88-169-191-86.subs.proxad.net) | 01:30 | |
| jfred | Woohoo! I got an standalone lipo battery charger and charged both my Pocket's batteries externally, and I think this might have revived them somewhat? Too early to really tell but they seem to be behaving better than they have in a while | 02:23 |
|---|---|---|
| jfred | Previously they would immediately drop down to 3.7 V or below even when the Pocket saw them as fully charged, but now they've been sitting at 4 V for a little bit while running. Which I think is closer to what it should be at full charge, looking at a reference for li-ion discharge voltage curves | 02:28 |
| minute | jfred: nice | 02:40 |
| jfred | (also I know I've said this before but having a laptop that can tell you the voltages across each of its battery cells at any time is awesome haha) | 02:41 |
| - paperManu_ (QUIT: Ping timeout: 252 seconds) (~paperManu@204.48.0.160) | 03:20 | |
| - paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@204.48.0.160) | 03:49 | |
| + mjw (~mjw@66.183.205.74) | 04:41 | |
| aloo_shu | would have been interesting to compare also open voltages w/o load, before and after the improvement | 05:41 |
| aloo_shu | to get an idea if internal and external charger have a different notion of 'full', and that's causing it | 05:41 |
| aloo_shu | but if true, after a cycle back on the internal charger, you would know | 05:42 |
| - voltaire28 (QUIT: Ping timeout: 265 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 07:05 | |
| - mjw (QUIT: Ping timeout: 245 seconds) (~mjw@66.183.205.74) | 10:05 | |
| + andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net) | 10:18 | |
| - andreas-e (QUIT: Client Quit) (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net) | 10:19 | |
| + mjw (~mjw@66.183.205.74) | 12:15 | |
| + gidzit (~gidzit@82-64-82-48.subs.proxad.net) | 12:16 | |
| + oliverD (~Thunderbi@user/oliverd) | 13:54 | |
| - oliverD (QUIT: Remote host closed the connection) (~Thunderbi@user/oliverd) | 13:54 | |
| + paperManu (~paperManu@204.48.0.160) | 14:11 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@66.183.205.74) | 14:15 | |
| - amospalla (QUIT: Ping timeout: 266 seconds) (~jordi@user/amospalla) | 14:34 | |
| + amospalla (~jordi@user/amospalla) | 14:36 | |
| - _justin_kelly4 (QUIT: Ping timeout: 245 seconds) (~justinkel@user/justin-kelly/x-6011154) | 16:02 | |
| + _justin_kelly4 (~justinkel@user/justin-kelly/x-6011154) | 16:17 | |
| - colinsane (QUIT: Remote host closed the connection) (~colinunin@97-113-85-96.tukw.qwest.net) | 16:50 | |
| + colinsane (~colinunin@97-113-85-96.tukw.qwest.net) | 16:51 | |
| - colinsane (QUIT: Remote host closed the connection) (~colinunin@97-113-85-96.tukw.qwest.net) | 16:51 | |
| + colinsane (~colinunin@97-113-85-96.tukw.qwest.net) | 16:54 | |
| - gidzit (QUIT: Ping timeout: 264 seconds) (~gidzit@82-64-82-48.subs.proxad.net) | 17:35 | |
| minute | we found out today that the new panel and mntsc drivers and fw actually work on the imx8mp | 17:58 |
| minute | and display v1 | 17:58 |
| minute | but! the display can't "wake up" from whatever gdm and gnome are doing to blank it | 17:58 |
| minute | and on sway, curiously, it can be disabled and reenabled with output disable and output enable, *but* will come only after a output DSI-1 mode 1920x1200 for some reason | 17:59 |
| minute | is this already the same behavior on the currently released versions? | 18:00 |
| + mjw (~mjw@66.183.205.74) | 18:24 | |
| amospalla | minute: I have some similar behaviour with display v1 and rk3588. | 19:13 |
| amospalla | oh wait, no, it was a barebox thing, not related to any new firmware. Sorry for the confusion. | 19:15 |
| josch | minute: i don't have a display v1 so i cannot test but the README.md of reform-system-image has link to old system images which you could flash to an sd-card and boot to see what happens | 19:17 |
| minute | josch: right, thanks. i thought i'd ask just in case someone could directly confirm this. | 19:23 |
| josch | minute: there are a bunch of forum posts about the display staying black when gnome resumes but they are all mixed with display flicker issues and other things and for platforms that are not imx8m+ so hard to say which one is relevant for the issue you see right now... | 19:24 |
| minute | yeah, the threads that i know are very confusing+confused | 19:27 |
| minute | just set up an mnt camera + obs to stream a camera feed pointed at the pocket display v1/imx8mp from the other side of the room to my development desktop :D | 19:28 |
| josch | haha the luxery XD | 19:30 |
| minute | mhm, the panel driver causes an oops with "i2c i2c-0: <i2c_imx_write> write timedout" when doing sudo rmmod panel-mnt-pocket-reform | 19:30 |
| minute | reads like there is some regulator wrongly attached in dts to the panel, lets see... | 19:31 |
| josch | minute: for the MNT camera you are choosing the RGB stream? YUV has some flicker effects for me... | 19:31 |
| josch | (RGB seems to work) | 19:31 |
| - qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit) | 19:33 | |
| minute | josch: interesting. so far YUV, let me try RGB, but i think i know what you mean. | 19:33 |
| josch | (it also depends on the resolution -- lower resolutions don't cause issues) | 19:34 |
| josch | minute: also don't let me distract you if you are busy please :) | 19:35 |
| minute | josch: correct, it's not really useable with the higher (usb3) resolutions + OBS on rk3588. this is some rk3588 related usb issue | 19:35 |
| josch | ooooh | 19:35 |
| josch | thank you for confirming! :) | 19:36 |
| minute | hmmm why the hell is this doing some i2c thing after unloading | 19:36 |
| minute | regulator_put... | 19:36 |
| josch | mnt july update informed me that there are more enjoyers of the blue usb-c silicon cable from media markt :D | 19:38 |
| minute | haha yesss, you caught me | 19:39 |
| minute | i was perplexed about that full aluminum connector housing :D | 19:39 |
| + qbit (~qbit@user/qbit) | 19:40 | |
| minute | ok, looks like the panel driver has unloaded anyway. strangely, the display v1 stays on and retains its image | 19:40 |
| minute | ah and after loading the panel driver, it doesn't come on again by default. maybe because of the whole init-in-enable hack | 19:41 |
| minute | wow, data abort oops in drm_panel_disable+0x13c/0x168 | 19:43 |
| minute | i'm wondering if the hdmi driver messes things up... | 19:45 |
| + AnimaInvicta (~AnimaInvi@88-169-191-86.subs.proxad.net) | 19:45 | |
| minute | btw would be interesting to attempt a barebox build for imx8mp | 19:53 |
| minute | as it has support for that iirc? | 19:53 |
| ^alex | we could test stuff on the imx8mp | 20:02 |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@66.183.205.74) | 20:06 | |
| minute | aha, i just removed all the (unused) regulator code from the panel driver now, no more kernel oopses | 20:16 |
| ^alex | Colonel Oops? does he outrank General Protectionpfault? | 20:20 |
| minute | one would think so | 20:40 |
| - _justin_kelly4 (QUIT: Ping timeout: 244 seconds) (~justinkel@user/justin-kelly/x-6011154) | 20:40 | |
| - Asmadeus (QUIT: Ping timeout: 268 seconds) (~asmadeus@user/meow/Asmadeus) | 20:42 | |
| ^alex | idk anything about military hierarchies, we just make bad posts on line | 20:48 |
| - potash6 (QUIT: Quit: The Lounge - https://thelounge.chat) (~potash@user/foghorn) | 20:51 | |
| + _justin_kelly4 (~justinkel@user/justin-kelly/x-6011154) | 20:54 | |
| minute | hm, i can remove and reload the panel driver now on imx8mp without crashes, but it's not behaving like i'd expect | 21:00 |
| minute | it attaches to the dsi host, but is never enabled | 21:00 |
| minute | nor prepared | 21:00 |
| + potash6 (~potash@user/foghorn) | 21:00 | |
| minute | why is linux drm always such a PITA... | 21:01 |
| minute | heh, at least by accident i found a more robust panel version probing mechanism | 21:06 |
| - rick_ (QUIT: Remote host closed the connection) (~m-x42ph2@m.n0id.space) | 21:06 | |
| + rick_ (~m-x42ph2@m.n0id.space) | 21:06 | |
| orva | Good things are often wrapped in pita | 21:16 |
| + mjw (~mjw@178.230.77.16) | 22:18 | |
| - colinsane (QUIT: Remote host closed the connection) (~colinunin@97-113-85-96.tukw.qwest.net) | 22:28 | |
| + colinsane (~colinunin@97-113-85-96.tukw.qwest.net) | 22:32 | |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@178.230.77.16) | 22:37 | |
| + Asmadeus (~asmadeus@user/meow/Asmadeus) | 22:54 | |
| minute | funny, i just figured out that display reset on mb1 with that new sysctl fw couldn't have worked because it's behind the latch, and the cli api didn't toggle the latch on set-gpio | 23:15 |
| - colinsane (QUIT: Remote host closed the connection) (~colinunin@97-113-85-96.tukw.qwest.net) | 23:19 | |
| + colinsane (~colinunin@97-113-85-96.tukw.qwest.net) | 23:22 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!