ikarso has quit [Quit: Connection closed for inactivity]
vagrantc has quit [Quit: leaving]
mckoan|away has quit [Ping timeout: 265 seconds]
mckoan|away has joined #u-boot
baltazar has quit [Ping timeout: 245 seconds]
baltazar has joined #u-boot
frytaped has joined #u-boot
Daanct12 has joined #u-boot
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #u-boot
vardhan has joined #u-boot
vardhan has quit [Ping timeout: 248 seconds]
naoki has quit [Remote host closed the connection]
naoki has joined #u-boot
rvalue has quit [Ping timeout: 245 seconds]
rvalue has joined #u-boot
rvalue has quit [Ping timeout: 252 seconds]
ungeskriptet_ has joined #u-boot
ungeskriptet has quit [Ping timeout: 260 seconds]
ungeskriptet_ is now known as ungeskriptet
rvalue has joined #u-boot
monstr has joined #u-boot
goliath has joined #u-boot
frieder has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
mckoan|away is now known as mckoan
mmu_man has joined #u-boot
jfsimon1981 has quit [Ping timeout: 265 seconds]
ikarso has joined #u-boot
rvalue has quit [Ping timeout: 265 seconds]
rvalue has joined #u-boot
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
jfsimon1981 has joined #u-boot
gsz has joined #u-boot
dsimic has quit [Ping timeout: 248 seconds]
dsimic has joined #u-boot
sszy has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
<LeSpocky>
given I have some myboard-revA.dts including myboard-common.dtsi including some soc.dtsi, is a myboard-common-u-boot.dtsi supposed to be picked up? asking because it seems like no.
<marex>
no
<marex>
you need myboard-revA-u-boot.dtsi which includes myboard-common-u-boot.dtsi
vardhan has joined #u-boot
mmu_man has quit [Ping timeout: 244 seconds]
<LeSpocky>
marex: thanks for confirming, that's what I figured from other examples now :-)
mmu_man has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #u-boot
frytaped has quit [Quit: WeeChat 4.4.2]
<calebccff>
sjg1: also a heads up about this patch, i guess i wasn't super clear about how your "swap the signature for board_fdt_blob_setup()" series broke mach-snapdragon, the v2 didn't actually fix the issue i bought up and 2025.01 is broken on snapdragon as a result :/
<sjg1>
calebccff: Oh dear, yes I remember reworking the patch for v2, but I suppose I still got it wrong. I'm please to see your patch
frytaped has joined #u-boot
naoki has quit [Quit: naoki]
monstr has joined #u-boot
frytaped has quit [Quit: WeeChat 4.4.2]
Daanct12 has quit [Quit: WeeChat 4.5.1]
frytaped has joined #u-boot
pbsds3 has joined #u-boot
tnovotny has joined #u-boot
mckoan is now known as mckoan|away
frytaped has quit [Ping timeout: 272 seconds]
frytaped has joined #u-boot
tnovotny has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
yann-kaelig has joined #u-boot
bwani54 has joined #u-boot
bwani54 has quit [Remote host closed the connection]
frytaped has quit [Quit: WeeChat 4.4.2]
frytaped has joined #u-boot
gsz has quit [Ping timeout: 245 seconds]
yann-kaelig has quit []
frieder has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
goliath has joined #u-boot
mckoan|away has quit [Ping timeout: 246 seconds]
mckoan|away has joined #u-boot
Slimey_ has joined #u-boot
goliath has quit [Quit: SIGSEGV]
m5zs7k_ has joined #u-boot
stgl has quit [Ping timeout: 252 seconds]
Kwiboo has quit [Remote host closed the connection]
agraf has quit [Ping timeout: 248 seconds]
Kwiboo has joined #u-boot
mckoan|away has quit [Ping timeout: 248 seconds]
Slimey has quit [Ping timeout: 248 seconds]
Slimey_ is now known as Slimey
jeeebz has joined #u-boot
mckoan|away has joined #u-boot
LordKalma has quit [Read error: Connection reset by peer]
jsmolic has quit [Read error: Connection reset by peer]
redbutton has quit [Ping timeout: 252 seconds]
stgl has joined #u-boot
Wouter0100 has quit [Read error: Connection reset by peer]
redbrain has quit [Ping timeout: 248 seconds]
jkt has quit [Ping timeout: 248 seconds]
m5zs7k has quit [Read error: Connection reset by peer]
j`ey has quit [Ping timeout: 272 seconds]
jybz has quit [Read error: Connection reset by peer]
jsmolic has joined #u-boot
MWelchUK6 has joined #u-boot
LordKalma has joined #u-boot
Wouter0100 has joined #u-boot
jclsn has quit [Ping timeout: 272 seconds]
MWelchUK has quit [Ping timeout: 272 seconds]
MWelchUK6 is now known as MWelchUK
j`ey has joined #u-boot
jclsn has joined #u-boot
redbutton has joined #u-boot
redbrain has joined #u-boot
jkt has joined #u-boot
agraf has joined #u-boot
m5zs7k_ is now known as m5zs7k
monstr has quit [Remote host closed the connection]
jfsimon1981 has quit [Remote host closed the connection]
<Tartarus>
Since Kwiboo asked in the rockchip channel, I'm testing moving to v6.13 device trees now, and I've got the email ready to send out once building / unit testing is done
<Kwiboo>
Tartarus: I did not even notice I asked in wrong channel :-), look like there is a build issue in CI: rk356x.dtsi was renamed to rk356x-base.dtsi
<Kwiboo>
I also see a few ValueError: Cannot parse 'clocks' in node 'clock-controller@ff440000'
joeskb7 has joined #u-boot
<Tartarus>
Kwiboo: I was just about to ask if you've got an idea about the clocks one
<Kwiboo>
Tartarus: including the new clock in bootph-all seem to fix the issue, or removing the added clocks props, adding bootph prop is probably best and most correct: https://paste.debian.net/hidden/2705b3b3/
<Tartarus>
Kwiboo: Thanks, I can do the -u-boot.dtsi for now and you can upstream it for eventually?
<Kwiboo>
yes, I should really start to upstream all Rockchip bootph props, do not think we have any one in upstream DT yet, all bootph props is still in -u-boot.dtsi :-)
<Tartarus>
Ah, ok
naoki has joined #u-boot
vardhan_ has joined #u-boot
vardhan has quit [Ping timeout: 252 seconds]
gsz has joined #u-boot
ikarso has joined #u-boot
<Tartarus>
Sigh, I think the bcc part didn't work
<marex>
Tartarus: everything is perfect on the rcar side I hope ? :)
<marex>
Tartarus: nothing in the 6.12..6.13 diff which particularly affects U-Boot , so I think we are all good here
<Tartarus>
sjg1: So, different topic. On top of v6.13 and after the patch I posted to fix ti/omap/omap4-panda-a4.dts, image.fit Just Works on ARCH=arm, should I actually make that a patch and post it, or do you not want to deal with any of the noise / fall-out from it?
<sjg1>
Tartarus: OK, yes I suppose the bootph tag is the best idea
<sjg1>
Tartarus: I think a patch would be nice, actually. People in kernel-land will learn about FIT eventually so we might as well start now :-)
<sjg1>
Also I haven't got back to the network-in-lab thing but I did start. Should get some time tomorrow morning
vagrantc has joined #u-boot
goliath has joined #u-boot
<Tartarus>
sjg1: OK, it'll be a bit, that device tree patch needs to go somewhere first and I'm sure if it's not in yet this'll blow up for someone else and that'll take forever to get over