<mmind00>
macc24: I don't have a super (...yet?) ... but that is probably simply a different display ... and missing correct timings and display init driver
<macc24>
mmind00: panel init sequence looks suspiciously similar to what's inside of panel-sitronix-st7701
<mmind00>
st7701 is actually not a panel but a panel->dsi encoder ... so that's probably to be expected
<mmind00>
macc24: looking at the DTS ... I guess you'll just need the initsequence from there and dump into a panel-driver
<macc24>
i did exactly that
<macc24>
and got the result, any ideas?
<mmind00>
pffffff ...sadly I'm not doing panel drivers on a daily basis ;-)
<mmind00>
macc24: are the stripes static or are the "moving"?
<macc24>
it looks like the panel smears out everything on y-axis
<macc24>
when i write to framebuffer they change
<mmind00>
like is that distorted output or no output at all
<macc24>
distrorted output
<mmind00>
ah, so the panel does get data ... but the panel init or timings are off I guess
<mmind00>
do you keep your panel-driver somewhere?
<mmind00>
darn memory of mine .... I somehow do remember the panel not working from the start, but can't for the life of me remember what did the final trick
<mmind00>
macc24: might any of the dsi->mode_flags change things (just seeing differences between Go-Advances and Go-Super panel drivers)
<macc24>
mmind00: i tried messing with that and it didn't work
archetech has quit [Quit: Konversation terminated!]
tlwoerner has joined #linux-rockchip
<ukleinek>
is it normal that in U-Boot I have ~5s delay between these two lines of output?:
<ukleinek>
PMIC: RK808
<ukleinek>
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
<macc24>
mmind00: relaxed timings a bit, no change
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
macc24 has quit [Ping timeout: 246 seconds]
field^Mop has quit [Ping timeout: 246 seconds]
tuxd3v has quit [Read error: Connection reset by peer]