gouchi has quit [Remote host closed the connection]
camus1 has joined #tegra
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
gouchi has joined #tegra
gouchi has quit [Remote host closed the connection]
gouchi has joined #tegra
gouchi has quit [Remote host closed the connection]
e1z0 has quit [Read error: Connection reset by peer]
e1z0 has joined #tegra
camus has quit [Ping timeout: 256 seconds]
camus has joined #tegra
camus has quit [Ping timeout: 256 seconds]
camus has joined #tegra
e1z0 has quit [Read error: Connection reset by peer]
e1z0 has joined #tegra
e1z0 has quit [Read error: Connection reset by peer]
e1z0 has joined #tegra
hexdump0815 has joined #tegra
<hexdump0815>
tagr: digetx: i'll test whatever you decide to finally implement regarding the display fix for nyan during the next days then
<hexdump0815>
tagr: while we are at nyan - do you maybe have an idea why u-boot if chainloaded from depthcharge is not able to properly initialize the display on the 1366x768 model of nyan big? it is just flickering wild in this case
<hexdump0815>
the kernel is working fine on this model and u-boot works fine on the full hd version of the nyan-big and on nyan-blaze with a 1366x768 panel
<hexdump0815>
the panel timings defined in the u-boot dts are for 1366x768 (only) and they match the used timing i for instance get out of xrandr when running xorg later exactly
<kwizart>
hexdump0815, u-boot has its own dtb IIRC, but I wonder if using edid would help in this case. I know edid support in the tegra-drm uboot would help (at least on paz00 where many have changed the default display)
camus has quit [Ping timeout: 256 seconds]
camus has joined #tegra
camus1 has joined #tegra
camus has quit [Ping timeout: 240 seconds]
camus1 is now known as camus
<tagr>
I've never worked with U-Boot's display support, but I know from working on the Tegra DRM bits that this can be a bit fiddly to get right
<tagr>
is it flickering but sometimes showing correct content or is it all wrong?
<tagr>
EDID is not necessarily going to help, if the programming sequences are wrong it isn't going to work no matter what mode you try to set
gouchi has joined #tegra
<jonasschwoebel[m>
<hexdump0815> "tagr: while we are at nyan..." <- On Surface RT the backlight only turns on at ~80% pwm duty cycle.
<jonasschwoebel[m>
Below the backlight flickers. Not sure if this is what you meant.
<jonasschwoebel[m>
But setting the duty cycle high enough fixes the problem.
<hexdump0815>
kwizart: yes i ment the u-boot dts for nyan-big - in there is a panel timing for 1366x768 defined
<hexdump0815>
tagr: it is flickering allways and the whole time while u-boot is active
<hexdump0815>
jonasschwoebel[m: it looks more like not getting the timings right than like a problem with the backlight - but who knows ... do you have an example of how to play with the pwm duty cycle?
<hexdump0815>
the strange thing is: it flickers like crazy if that (proably correct) panel timing is in the dts and if i remove this timing it only flickers once at the beginning and is calm then (still no display output though)
<hexdump0815>
i think the flickering is more like some mode switching flicker
<jonasschwoebel[m>
Write the pwm register directly. The uboot pwm stuff didn't work Iirc.
<jonasschwoebel[m>
Or just set the brightness to max in the devicetree.
<tagr>
there's no such thing as "mode switch flicker", really
<tagr>
at least not with eDP
<hexdump0815>
tagr: i just tried to describe how it looks like