Dear Rob Herring,
In message 515EED36.9090305@gmail.com you wrote:
The stack size limit only comes into play when bootm runs and starts moving initrd and dtb to high addresses below the stack. At that point, the stack size does become limited because only 4KB (recently increase from 1KB) of space is reserved. So I had this in mind when I started
This looks to be conceptually broken to me. You cannot just lmb_reserve() arbitrary amounts of memory, when the documented, pubished memory map clearly states that this memory is "free", and in use for the downward growing stack. If you need memory, you must reserve it in a clearly documented way.
A part of the problem appears to be that it's actually very difficult to even understand how the mnemory concept of LMB has been designed - it it was designed at all. Is there any related documentation?
debugging my environment getting corrupted and saw large buffers on the stack. My problem was ultimately that blank lines in mvenvimage input files are not handled correctly giving intermittent issues with the env import. I'm still not clear why the issue was intermittent, but I think mkenvimage should skip/remove blank lines. I still need to make a fix for that.
No, it should not. It is supposed to keep the very formatting chosen by the implementor.
The core of the problem is the illegal, and totally undocumented assumptions LMB appears to be making.
_This_ is what needs to be fixed.
Best regards,
Wolfgang Denk