<jernej>
I don't have time to dig into it, but it seems some data is stored on emmc
vagrantc has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
tnovotny has quit [Server closed connection]
tnovotny has joined #linux-sunxi
ftg has joined #linux-sunxi
paulk1 has quit [Ping timeout: 480 seconds]
paulk1 has joined #linux-sunxi
apritzel has joined #linux-sunxi
tnovotny has quit [Quit: Leaving]
hlauer has joined #linux-sunxi
<ynezz>
jernej: ah, cool
<ynezz>
looks like it's i2c eeprom
<ynezz>
"If the board has corrupted EEPROM (or it's very old without one) a sector in the MMC can be used as backup storage." #define OLIMEX_MMC_SECTOR0x0F/* One sector before SPL */
JohnDoe_71Rus has quit []
evgeny_boger has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
<jernej>
ynezz: I failed to find EEPROM on schematic
machinehum has quit [Ping timeout: 480 seconds]
hlauer has quit [Ping timeout: 480 seconds]
machinehum has joined #linux-sunxi
<apritzel>
jernej: yeah, I found that board detection code as well yesterday
<apritzel>
but it actually looks a bit over the top to me, since we probably just need to know whether it's a Micrel or Realtek PHY?
<apritzel>
which we should be able to find more easily, because the PHY is autodetected
<apritzel>
ynezz: so I have one question: did Ethernet work with pure mainline U-Boot v2022.01, with the RevK Micrel PHY?
<apritzel>
so without specifying some CONFIG_GMAC_TX_DELAY value?
bauen1 has joined #linux-sunxi
<libv>
is this delay because of how long the traces are and how they are routed, or only because of the phy?
<libv>
and are there board revisions which had the traces, and only the traces, altered