<daniels>
leowt: two unrelated problems then - one, you need to set up the i2c bus for ddc/edid, and then the other is that you need to find a supported resolution
<daniels>
leowt: see hdmiphy_v13_configs in drivers/gpu/drm/exynos/exynos_hdmi.c for the list of supported configs
<daniels>
leowt: *pixel clocsk
<leowt>
daniels yesterday i was able to fix the address of i2c for ddc, then i had somekind of signal fix
<daniels>
leowt: if your selected mode doesn't have that pixel clock, it's not going to work
<leowt>
daniels, sorry i cannot undersand that
<leowt>
isnt phy supposed to be somekind of ethernet through hdmi?
<daniels>
leowt: no, phy isn't ethernet
<daniels>
leowt: phy is short for physical - it's a physical interface to some kind of connector
<leowt>
i see
<daniels>
leowt: every display mode has a pixel clock / frequency listed with it
<daniels>
leowt: in that config table, you can find the list of pixel clocks which are supported by the exynos hdmi block
<daniels>
leowt: if the mode you want to set uses a different pixel clock, you cannot use it with exynos4 hdmi
<leowt>
daniels, and what am i supposed to do? change the bootargs somehow?
<daniels>
leowt: i don't know where your edid/1920x1080.bin comes from, but you need to use a different one which has a clock fitting into one of those supported modes
<daniels>
ah, it's built in ... yeesh
<daniels>
try 1024x768.bin perhaps
amitk has quit [Quit: leaving]
<leowt>
daniels, i dont know exactly what those bin files are, but they are to be used when no cec is available
<leowt>
i took those from odroid sources
<leowt>
on the original kernel they are also provided and borrowed from odroid sources
leowt has quit [Remote host closed the connection]
<liquidAcid>
Wizzup, thx, i was thinking about doing something similar for u2/u3
<Wizzup>
:-)
<Wizzup>
Someone asked me recently about a working mainline u-boot binary
<Wizzup>
since he couldn't get it to work
<Wizzup>
also, I am not sure if it is different for the X2, but for the U2 and U3, eMMC u-boot was quite a different, right/
<Wizzup>
You couldn't just dd to it using their emmc to sd convertor at least
<sjoerd>
eMMC boot is always from the eMMC boot partition
<liquidAcid>
no, i think you had to unlock the area of the emmc first
<sjoerd>
while for SD it's from the start of the normal data
<Wizzup>
right, thus you cannot access it from their 'emmc to sd convertor'
<Wizzup>
perhaps worth a mention somewhere at some point
<sjoerd>
I thought you could
<Wizzup>
I didn't manage last time I tried
<liquidAcid>
Wizzup, correct, you need to bootstrap this from one of the vendor images
<liquidAcid>
iirc you just need to write something to a sysfs node
<sjoerd>
Yes eMMC boot is r/o by default unless you turn it of
<liquidAcid>
and then, modulo the sector offset, you can write bl1/bl2/tszw to the device
<Wizzup>
aaah...
leowt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<liquidAcid>
Wizzup, from which device do you boot your u3?
<Wizzup>
sd card
<Wizzup>
but I don't have an eMMC card -- a friend has one
<liquidAcid>
Wizzup, if you've got some time, could you check if my guide also works for you (replacing the x2 dtb with the u3 of course, and the other modifications i pointed out)?
<Wizzup>
I can test it for the u2 later :)
<liquidAcid>
speaking of the u2, i think we could just rip out most of the empty section in the u3 article and only link to the u2 article (since on the level of software the two devices are identical)
<Wizzup>
I think it links to the u2 one already mostly
<liquidAcid>
yes, but it has all these empty section, which are kinda superfluous, in particular since they imply that content is missing there