19:40 <steev> narmstrong: have you had a chance to look into 1360x768? I am assuming if I were to do it, I’d need to edit meson_venc and add something like a 768p entry there like the 1080p but, I have no idea how to get the various numbers

19:42 <narmstrong> steev: no, there is no such entry because I derive them from the timings stored in the edid, like other monitor modes, and i check against how amlogic programs this mode and it’s also correct...

19:50 <steev> I’m not saying 1366x768 isn’t correct or that the timings are wrong. I’m asking what would be needed to be done to add in a 1360x768 entry - something akin to https://github.com/hardkernel/linux/blob/odroidc2-3.16.y/drivers/amlogic/hdmi/hdmi_tx_20/hdmi_tx_video.c#L524

19:51 <steev> Hang on let me find it not on on my phone

19:53 <steev> https://github.com/hardkernel/linux/blob/odroidc2-v3.16.y/drivers/amlogic/hdmi/hdmi_tx_20/hdmi_tx_video.c#L524

20:04 <steev> basically, if i do... cvt 1360 768 60; xrandr --newmode "1360x768_60.00" 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync; - the display becomes entirely usable - but the edid for the display *only* reports 1366x768

20:06 <steev> or well, it should, but that doesn't seem to be the case

20:08 <steev> ah right, last step - xrandr --output HDMI-1 --mode 1360x768_60.00

20:09 <steev> https://usercontent.irccloud-cdn.com/file/UK3jz6ht/1532808582.JPG

20:27 <steev> but, that's only per user, so e.g. when it kicks out to the password prompt, it goes back to the fuzzy display because xrandr's resolution isn't set there

22:45 <steev> well, i have a fix for X, so that's good, i test if the resolution is set to 1366x768 and if it is, just shuffle it on over to 1360x768. unfortunately, i haven't been able to do the same for the console yet