umbramalison has quit [Quit: %So long and thanks for all the fish%]
frieder has joined #u-boot
vulpes2[m]111117 has joined #u-boot
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 240 seconds]
vulpes2[m]111117 has joined #u-boot
vulpes2[m]111114 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 246 seconds]
vulpes2[m]111117 has joined #u-boot
sszy has joined #u-boot
vulpes2[m]111114 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 245 seconds]
vulpes2[m]111117 has joined #u-boot
rockosov has quit [Ping timeout: 245 seconds]
rockosov has joined #u-boot
vulpes2[m]111114 has quit [Ping timeout: 245 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 240 seconds]
vulpes2[m]111117 has joined #u-boot
<pivi>
Tartarus: yep, marcel is going to send a new version today fixing the couple of hiccups on the rst found by the azure CI and integrate the feedback from NishanthMenon
vulpes2[m]111114 has quit [Ping timeout: 245 seconds]
sng has quit [Remote host closed the connection]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 246 seconds]
vulpes2[m]111117 has joined #u-boot
vulpes2[m]111114 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 246 seconds]
vulpes2[m]111117 has joined #u-boot
mrnuke has quit [Ping timeout: 252 seconds]
mrnuke has joined #u-boot
vulpes2[m]111114 has quit [Ping timeout: 240 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 246 seconds]
vulpes2[m]111117 has joined #u-boot
frieder has quit [Ping timeout: 252 seconds]
vulpes2[m]111114 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 240 seconds]
vulpes2[m]111117 has joined #u-boot
vulpes2[m]111114 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has joined #u-boot
sng has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has quit [Ping timeout: 240 seconds]
vulpes2[m]111114 has joined #u-boot
vulpes2[m]111117 has quit [Ping timeout: 246 seconds]
vulpes2[m]111114 has quit [Client Quit]
vulpes2[m]111114 has joined #u-boot
ezulian has quit [Quit: ezulian]
ezulian has joined #u-boot
lucascastro has quit [Ping timeout: 250 seconds]
mmu_man has joined #u-boot
frieder has quit [Ping timeout: 246 seconds]
frieder has joined #u-boot
Net147 has quit [Quit: Quit]
Net147 has joined #u-boot
Net147 has joined #u-boot
Net147 has quit [Changing host]
sng has quit [Remote host closed the connection]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
<LeSpocky>
marex: don't know how familiar you are with at91 SoCs, but I found out U-Boot does not set anything in the config register of the PMECC and I suspect that to be the cause for the slow NAND flash access
<marex>
LeSpocky: not at all ;-)
<LeSpocky>
well then nevermind :-) (it's a hw ecc decoder for nand flash)
<marex>
LeSpocky: wasnt there the previous maintainer ?
<marex>
I recall I touched some at91 stuff in a rather insensitive manner (because of a security fix) and the maintainer was not very happy I worked around them (obviously)
<marex>
ah, Eugen I think
<marex>
LeSpocky: did you try talking to Eugen ?
<LeSpocky>
not yet
<LeSpocky>
the atmel raw nand driver has no explicit maintainer in u-boot currently
<marex>
LeSpocky: btw are you booting from raw NAND ?
<marex>
LeSpocky: maybe the bootrom fills the configuration and if you are not booting from raw NAND, the controller is left unconfigured
<LeSpocky>
not yet, but my goal is to do that
<LeSpocky>
marex: that's possible, but it should work nevertheless … I had that running on a modified sama5d27-som1-ek before
<LeSpocky>
one use case we have is having the u-boot env in raw nand or ubi on raw nand, boot from sd card and still have the u-boot env accessible
<LeSpocky>
I'll dig around some more
<marex>
LeSpocky: ACK, I can only provide generic advice here, sorry
<LeSpocky>
no problem, I just wanted to report progress
<LeSpocky>
raw nand maintainership changed and on at91 arch it's still a mixture of old drivers and new dm based driver
<marex>
sigh
<LeSpocky>
sam9 and sama5 having different capabilities, and people at microchip responsible changing more then one time in the last few years
sng has quit [Read error: Connection reset by peer]
sng has joined #u-boot
persmule has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
mmu_man has quit [Ping timeout: 246 seconds]
mmu_man has joined #u-boot
<sjg1>
Tartarus: Yes it is designed to run in two modes. I sent a patch to stop it resetting the state after each commit. When used with -v that might be closer to what you want. I'm not sure if it will cause other problems, though
<sjg1>
Tartarus: Of course, while building is building in one terminal, you can always query it in another
<Tartarus>
I _think_ with -v it was even harder to follow the output
<Tartarus>
all of my real uses of buildman have a wrapper, so, I don't really mind
<Tartarus>
it's just I think non-obvious
<Tartarus>
but I could be wrong
<Tartarus>
I think what I was expecting was to be able to do something like...