Open Source Software Developer working on various things (mostly embedded Linux).
Other interests: music, art, photography, old computers, etc.
| Age | 24 |
| Pronouns | they/them, he/him |
| Codeberg | https://codeberg.org/Danct12 |
| GitHub | https://github.com/Danct12 |
| Support me on Patreon | https://patreon.com/Danct12 |
| My weblog/page | https://danct12.github.io |
| TMA (for my favorite modules) | https://modarchive.org/member.php?97107 |
| more of me | https://tech.lgbt/@danct12 |
booted up my orange pi 5 again after months of nothing
i was amazed that there's a broken wine package in arch linux ports which urged me to try hangover
Ooh okay, this is definitely a different issue from mine.
Perhaps VOP2 really needs a reset? I'll have to spin up a U-Boot hack that assert/deassert soft rst on VOP. 🙄
(you can really tell i'm tired of debugging this issue)
I know some people say "reset the panel" or something like that, but I've said it before, I already tried that and that didn't do anything.. and so does powering down the panel.
This begs the question.. does this actually power down the display? I feel like if anything, powering it down completely should fix some other issue if reset doesn't.
or.. this must be a bug in the DSI controller, but doesn't seem to make any sense to me since I'm able to send commands and receive them as is.
And yes, I already tried to soft reset both the DSI, DSI PHY and even VOP2.
