Patch Set 3:

So it sounds like we need a way to tie in the Kconfig to this allocation (if possible). Have you looked into various options?

In the old days of bounce buffers and non-relocatable ramstage on x86, it would have been fragile for payload to access back to ramstage program. If I read the source correctly, ramstage heap became part of the hand-of-buffer with FIT payloads. Do we really want to allow that?

I think lib/device_tree.c and lib/fit_payload.c should malloc() from a completely separate heap.

I'm not up on the details of this sharing. Is the region just referenced or is it reused for its own malloc implementation?

View Change

To view, visit change 32392. To unsubscribe, or for help writing mail filters, visit settings.