<junari>
I don't have radxa, only walnutpi and x96qpro+, I haven't made patches for it
<junari>
I'm slowly making an HDMI and usb3 output right now, but that takes a lot of time I don't have. I think usb3 is an easier target. Anyway, any input would be helpful
<dlan>
great! I can test on radxa, do they work well on these boards, is there any pending issue before sending out to mailing list?
<dlan>
I'd be interested in HDMI, but do not have much experience..
<dlan>
since there are usb2? working, so usb3 isn't that urgent
<junari>
code cleanup is necessary. Also allwinner has greatly changed the frequency and voltage dependence on different versions of the same die
<Lightsword>
junari, should that work on other h616 boards using emac1?
cnxsoft has joined #linux-sunxi
<junari>
nope, controller is different
<junari>
но там единственная проблема в тактировании ephy
<junari>
but the only problem there is the ephy clocking.
<dlan>
do you mean phy25m clock?
<junari>
The T507 does not have the ephy ac300 and both ethernet work with some patches
cnxsoft has quit [Ping timeout: 480 seconds]
<junari>
Yes. The built-in ephy needs to be clocked with pwm
<dlan>
junari: is 'iuncuim' also you? commiter from patch, I'm trying to map id with people..
<junari>
Yes
<dlan>
great
<Lightsword>
junari, I've been trying to get emac1 working on a h616 board but have been completely unable to bring up the i2c3 in a usable state, the ac300 phy on a h616 won't function without i2c3 working right?
<dlan>
I haven't checked emac1 (ac300), but for emac0, the phy25m is optional, which really depend on hw design, for radxa board, it explicitlt use external xtal, so the internal phy25m clock isn't necessary
<Lightsword>
the ac300 phy on a h616 is controlled via i2c3(twi3) right? I've been trying all sorts of different patches to try and initialize it(the i2c3 interface) but no matter what I do I always get this error "i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0"
<junari>
Lightsword: That's right, but I haven't looked into it. I don't have the right device
<junari>
dlan: Yes, this is optional if an external crystal oscillator is used
<Lightsword>
junari, so second eth interface on T507 uses external phy and doesn't use i2c3 at all?
zamon has joined #linux-sunxi
<junari>
yes, it doesn't have ac300 at all
junari has quit [Remote host closed the connection]
radxanaoki has joined #linux-sunxi
junari has joined #linux-sunxi
junari has quit [Remote host closed the connection]
junari has joined #linux-sunxi
zamon has quit [Remote host closed the connection]
Schimsalabim has quit [Ping timeout: 480 seconds]
zamon has joined #linux-sunxi
junari has quit [Remote host closed the connection]
junari has joined #linux-sunxi
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
junari has quit [Remote host closed the connection]
hexdump0815 has joined #linux-sunxi
vagrantc has joined #linux-sunxi
hexdump02 has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
zamon has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
zamon has joined #linux-sunxi
Schimsalabim has joined #linux-sunxi
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
gsz has joined #linux-sunxi
gsz has quit []
gsz has joined #linux-sunxi
chewitt has joined #linux-sunxi
jgfh has joined #linux-sunxi
dfas has quit [Read error: Connection reset by peer]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
hexdump01 has quit []
hexdump01 has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
<zamon>
I applied the above u-boot patches on 2025.04-rc5. But the patch doesn't have defconfig for my orangepi 4A, so I copied from avaota-a1_defconfig and did some tiny changes. After all, u-boot could run
<dlan>
must check code, maybe both uboot and sunxi-tools
<dlan>
where the actual address used
<zamon>
dlan: Hey, I think I get the answer. It's likely that Image was bigger than 0x1000000 and overwrote the fdt which loaded first :( I tried other undocumented address which worked as well :)
<paulk>
AFAIK there's no particular constraint on the load addresses anymore
digetx has quit [Ping timeout: 480 seconds]
digetx has joined #linux-sunxi
radxanaoki has quit [Quit: radxanaoki]
mripard has joined #linux-sunxi
mripard__ has quit [Ping timeout: 480 seconds]
hentai has joined #linux-sunxi
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-sunxi
ungeskriptet has quit [Remote host closed the connection]