frieder has quit [Remote host closed the connection]
mncheck has quit [Ping timeout: 244 seconds]
mncheck has joined #u-boot
_sfo has quit [Ping timeout: 246 seconds]
goliath has joined #u-boot
sylensky[m] has joined #u-boot
mncheck has quit [Ping timeout: 246 seconds]
mncheck has joined #u-boot
frieder has joined #u-boot
ikarso has joined #u-boot
jclsn has quit [Ping timeout: 260 seconds]
tnovotny has joined #u-boot
Adrian has joined #u-boot
Adrian___ has quit [Ping timeout: 245 seconds]
jclsn has joined #u-boot
jclsn has quit [Ping timeout: 264 seconds]
jaganteki has quit [Ping timeout: 246 seconds]
sszy has joined #u-boot
qqq has quit [Remote host closed the connection]
<sng>
I am getting github CI failures, which I believe are due to f586cdaef9. anyone else getting these?
<sng>
these are buildman errors - PermissionError: [Errno 13] Permission denied: '../.bm-work'
qqq has joined #u-boot
iprusov has quit [Ping timeout: 245 seconds]
sng has quit [Remote host closed the connection]
iprusov has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
jclsn has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
jclsn has quit [Ping timeout: 246 seconds]
iprusov has quit [Quit: WeeChat 3.5]
sng has joined #u-boot
<pivi>
NishanthMenon, Tartarus : let me know what you think on this verdin-am62 series, I think that the DTS sync should not be a reason for postponing
<marex>
pivi: is the DT sync bringing in anything significant ?
<NishanthMenon>
marex: pivi: sync with upstream kernel brings in almost all the nodes that we have been maintaining out of tree and making kernel sync back to u-boot harder to do - including fixes for mmc etc. i am just in the middle of doing the same atm - you should see a series later today
hanetzer has joined #u-boot
jclsn has joined #u-boot
* marex
reminds marex not to ask about the GPU node
<marex>
NishanthMenon: I guess rebase on top of that makes sense then
soxrok2212 has quit [Read error: Connection reset by peer]
sng has quit [Remote host closed the connection]
soxrok2212 has joined #u-boot
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
sng_ has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sakman has quit [Read error: Connection reset by peer]
tnovotny_ has joined #u-boot
<pivi>
NishanthMenon: what I am trying to say is that the verdin-am62 addition does not even conflict with the DT series update, so I do not see reason to serialize the twos
<pivi>
NishanthMenon: the binman change was more tricky, but this is done
<NishanthMenon>
pivi: that would'nt make sense as the u-boot.dtsi files are going to be minimal
<NishanthMenon>
pivi: please see the diffstat - timers, and bunch of other stuff that is now inherited from SoC.dtsi files directly
<pivi>
NishanthMenon: we can just cleanup the u-boot.dtsi with a follow-up commit, it does not look like a complicate job. To me in the end it really depends when/if Tartarus is planning to merge the DTS sync series you just updated, I would prefer to not postpone merging it for much longer, of course 1 week does not make any difference to me
mmu_man has joined #u-boot
<sjg1>
Tartarus: I don't really understand the testBranchWithSlash() failure, since this test has been there for eons. Perhaps it didn't run for some reason?
<sjg1>
Tartarus: But definitely it is accessing the directory above, which is not allowed on azure
<NishanthMenon>
pivi: at the baremin, without the sync, you are going to have broken mmc/sd and emmc (as far as I can see)
<pivi>
NishanthMenon: really? from what I was told Marcel tested the verdin-am62 series and it was working. And we do boot always from eMMC on our device. You mean that after the DTS sync it will eventually stop working?
<sjg1>
Tartarus: But yes, a quick fix by the look of it. I am running azure CI now
<pivi>
NishanthMenon: in any case, if this get merged soonish I do not see any issue, all fine, we'll just rebase on top of it
<NishanthMenon>
pivi: see the *tap delay changes.
<NishanthMenon>
pivi: without the tap delay changes, we had mixed results, so, you might have gotten lucky there.
<sjg1>
Tartarus: It seems to pass now. Will send the patch
m5zs7k has quit [Ping timeout: 264 seconds]
m5zs7k has joined #u-boot
sng has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
<sjg1>
Tartarus: I think it was actually this: 372b44589f2 bulldman: Set up output_dir earlier
<sjg1>
Tartarus: Since before them some of the tests would not need to set it up at all
<Tartarus>
Ah, ok
sakman_ is now known as sakman
monstr has quit [Remote host closed the connection]
vagrantc has joined #u-boot
Leopold_ has joined #u-boot
Leopold has quit [Ping timeout: 240 seconds]
ikarso has joined #u-boot
<Tartarus>
pivi: So, I gather you would really prefer this platform to be included in v2023.10 rather than v2024.01. And spelling out the dates like that, I can certainly see why...
<Tartarus>
NishanthMenon: Do you have all of the DTS resync stuff posted, for these platforms now?
xypron has quit [Ping timeout: 245 seconds]
teejay has joined #u-boot
<Tartarus>
As it seems like there might be something networking related that needs sorting, or am I confusing things?
<marex>
Tartarus: maybe toradex should have their own upstreaming tree and send PRs from that ;/
<Tartarus>
That may ease some of the bottlenecks, yes, but at heart there's still a conflict/issue with the general dts stuff here
<Tartarus>
(And I should, but don't want to, think what state the imx dts files are in atm)
<NishanthMenon>
Tartarus: for am62 - beagleplay is incoming in a few mins.. trying to figure out the docs side of things
tchebb has quit [Ping timeout: 245 seconds]
mmu_man has quit [Ping timeout: 260 seconds]
xypron has joined #u-boot
<Tartarus>
pivi: And on a tangent (as I go and rework the "writer" u-boot-test-hooks script I had to handle binman) I'd love to see how toradex is handling some parts of U-Boot CI
xypron has quit [Ping timeout: 240 seconds]
mmu_man has joined #u-boot
tchebb has joined #u-boot
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
<pivi>
Tartarus: yes, that would be my desire. we would really love to have our CI/Lava start running test on master on TI AM62, and for that we need to have it merged.
<pivi>
Tartarus: on the actual challenge, well, I'll let you know. We normally test a whole OE build image, that is integrating the latest u-boot/linux master, so no much additional integration apart getting it building in OE
<Tartarus>
pivi: Ah, so you don't run the u-boot pytest suite too?
<pivi>
Tartarus: nope, we run our standard whole image test suite, just using the latest u-boot
<Tartarus>
ok
<pivi>
Tartarus: mainly is boot or integration regression that we spot
<pivi>
Tartarus: that is already helping, as you know ;-)
goliath has quit [Quit: SIGSEGV]
<Tartarus>
Yes, it's a good start :)
xypron has joined #u-boot
xypron has quit [Ping timeout: 260 seconds]
xypron has joined #u-boot
xypron has quit [Ping timeout: 260 seconds]
tchebb_ has joined #u-boot
mmu_man has quit [Ping timeout: 260 seconds]
tchebb has quit [Ping timeout: 264 seconds]
xypron has joined #u-boot
xypron has quit [Ping timeout: 260 seconds]
mmu_man has joined #u-boot
xypron has joined #u-boot
<sjg1>
Tartarus: OK I will run on azure too in future
<Tartarus>
sjg1: Maybe not every PR every time (it's slower than gitlab), but at least when you make changes to *man tools, getting a once-through on Azure might be good too
Leopold_ has quit [Remote host closed the connection]
Leopold has joined #u-boot
xypron has quit [Ping timeout: 260 seconds]
sng_ has joined #u-boot
sng has quit [Read error: Connection reset by peer]