[PATCH v4 00/27] Make LMB memory map global and persistent
Tom Rini
trini at konsulko.com
Wed Sep 4 02:20:33 CEST 2024
On Mon, 26 Aug 2024 17:29:13 +0530, Sughosh Ganu wrote:
> This is a follow-up from an earlier RFC series [1] for making the LMB
> and EFI memory allocations work together. This is a non-rfc version
> with only the LMB part of the patches, for making the LMB memory map
> global and persistent.
>
> This is part one of a set of patches which aim to have the LMB and EFI
> memory allocations work together. This requires making the LMB memory
> map global and persistent, instead of having local, caller specific
> maps. This is being done keeping in mind the usage of LMB memory by
> platforms where the same memory region can be used to load multiple
> different images. What is not allowed is to overwrite memory that has
> been allocated by the other module, currently the EFI memory
> module. This is being achieved by introducing a new flag,
> LMB_NOOVERWRITE, which represents memory which cannot be re-requested
> once allocated.
>
> [...]
Applied to u-boot/next, thanks!
--
Tom
More information about the U-Boot
mailing list