<apritzel>
I mean there should be some crash dump already, given that the handlers are compiled in and the abort source is enabled (thinking of SError here, which isn't, normally)
<NishanthMenon_>
apritzel, https://gist.github.com/nmenon/f7af7173b334f57914f3d7ba933abe65 is an example -> if i disable ARMv8 tf-a crash reporting.. and lets say u-boot drivers or shell does some nonsense write, the bus error sticks till kernel enables handlers.. and then a bunch of backtracking before we can figure out it is actually the u-boot generates the dump
<apritzel>
NishanthMenon_: yeah, been there exactly!
<NishanthMenon_>
apritzel, i can trap in tf-a for sure.. but that is'nt nice since it hides the proper kernel reporting
<apritzel>
I fixed this by justing enabling the SError bit in U-Boot, and was thinking of a patch already
<NishanthMenon_>
apritzel, oooh ... will be interested in seeing your patch - will save my community a bunch of pain
rcn-ee_ has quit [Read error: Connection reset by peer]
mmu_man has quit [Ping timeout: 240 seconds]
apritzel has joined #u-boot
<apritzel>
NishanthMenon_: great to hear. If I don't forget it, I will send a patch this time. I wonder what starts popping up then on some boards ... ;-)
<Androo>
Would it be possible to execute a boot script not in a formatted partition (written at a specific offset on mmc0, for instance)? Or must I have it in a partition? Is the better option to just override bootcommand in the environment?
<Tartarus>
Yes, you can load in to memory from whatever
<Tartarus>
mmc read ....
<Androo>
ooo, somehow I missed that argument. Much appreciated.
Androo has quit [Quit: leaving]
___nick___ has quit [Ping timeout: 256 seconds]
vagrantc has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
<apritzel>
NishanthMenon_: ha, found my old patch, basically what you wrote, just in start.S ;-)