LordKalma has quit [Quit: Server has probably crashed]
LordKalma has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-sunxi
libv_ is now known as libv
JohnDoe_71Rus has quit []
bauen1 has quit [Ping timeout: 480 seconds]
cnxsoft has quit [Ping timeout: 480 seconds]
cnxsoft has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
grming has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
codekipper has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
cnxsoft has quit []
sh1 has quit [Ping timeout: 480 seconds]
sh1 has joined #linux-sunxi
junari_ has quit [Read error: Connection reset by peer]
Daanct12 has joined #linux-sunxi
Danct12 has quit [Read error: Connection reset by peer]
Daaanct12 has joined #linux-sunxi
Daanct12 has quit [Ping timeout: 480 seconds]
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
ftg has joined #linux-sunxi
anarsoul has quit [Ping timeout: 480 seconds]
<apritzel>
DasChaos: that would have been U-Boot master at the time of sending
<apritzel>
so should probably still apply somewhat cleanly on top of 2023.01, I guess
<DasChaos>
apritzel: thank you then I will search with the given date
<apritzel>
DasChaos: I can push it to my github, if that helps
<DasChaos>
No if I find the correct commit it's okay, should be fine with the date.
<DasChaos>
I tried implementing awboot into yocto but i failed, because using a different compiler then defined in readme, it won't build. So now I want to try U-Boot with the patch to test it and maybe report issues with it.
anarsoul has joined #linux-sunxi
<apritzel>
DasChaos: applied cleanly for me on top of v2023.01-rc3
<apritzel>
DasChaos: any testing and comments are highly appreciated
<DasChaos>
apritzel: Thanks for testing
<apritzel>
there are some conflicts when applied on top of v2023.01, looks like trivial defconfig file changes, though
<apritzel>
DasChaos: if you apply on top -rc3, then "git rebase v2023.01", git fixes it up automatically
<DasChaos>
Nice, btw i also got mainline 6.0.1 working on t113 with a 26 line patch I found on GitHub
<apritzel>
what's the significance of v6.0.1?
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
<apritzel>
linux-next should contain the required clock fixes, and that should work already
<apritzel>
HackerKkillinghisLGA775cpuPent: jernej and I are loosely working on upstreaming, but it's not the highest priority at the moment, and we are both quite busy
<HackerKkillinghisLGA775cpuPent>
apritzel: nice
<DasChaos>
apritzel: Yeah i found that already, is this needed in addition to the other patch?
<apritzel>
HackerKkillinghisLGA775cpuPent: I sent the first patch already, but the maintainer asked tough questions, so I need to dig into how to make this coexists with other PHY drivers
<DasChaos>
<apritzel> "what's the significance of v6.0...." <- Just was the version i found the patch for, upgrading it was an later goal
DarkNeutrino has quit [Read error: Connection reset by peer]
<DasChaos>
I'm just working it step by step through
DarkNeutrino has joined #linux-sunxi
<apritzel>
DasChaos: just use linux-next, or latest 6.2-rc plus smaeul's clock fixes, and avoid wasting time with outdated code
<apritzel>
DasChaos: if you find issues, you can report them, that would help both you and everyone else
<DasChaos>
Thanks, yeah didn't know that they are already in linux-next
<DasChaos>
Really big test can be made in about one month, because there I will probably receive the first custom PCB that has t113 with more hardware on it.
<DasChaos>
Right now I'm using the mango pi
<DasChaos>
apritzel: Would it be interesting for you, if I later publish my yocto layer for t113?