summaryrefslogtreecommitdiff
path: root/util/cbfstool/lz4/NEWS
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@google.com>2020-05-15 15:43:15 -0700
committerPatrick Georgi <pgeorgi@google.com>2020-05-26 15:15:21 +0000
commit69395742b8e45433e42c54e6cf8e67a692f923e9 (patch)
tree9b54309edf00f03dd7bb6739348f548c9af86f3e /util/cbfstool/lz4/NEWS
parentafaae8aa00d59a1a74e7f7891d8def8cc21d9eb2 (diff)
device: Move resource allocation into a separate compilation unit
This change moves the resource allocator functions out of device.c and into two separate files: 1. resource_allocator_v3.c: This is the old implementation of resource allocator that uses a single window for resource allocation. It is required to support some AMD chipsets that do not provide an accurate map of allocated resources by the time the allocator runs. They work fine with the old allocator since it restricts itself to allocations in a single window at the top of the 4G space. 2. resource_allocator_common.c: This file contains the functions that can be shared by the old and new resource allocator. Entry point into the resource allocation is allocate_resources() which can be implemented by both old and new allocators. This change also adds a Kconfig option RESOURCE_ALLOCATOR_V3 which enables the old resource allocator. This config option is enabled by default currently, but in the following CLs this will be enabled only for the broken boards. Reason for this split: Both the old and new resource allocators need to be retained in the tree until the broken chipsets are fixed. Change-Id: I2f5440cf83c6e9e15a5f22e79cc3c66aa2cec4c0 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/41442 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Mike Banon <mikebdp2@gmail.com> Reviewed-by: Nico Huber <nico.h@gmx.de> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'util/cbfstool/lz4/NEWS')
0 files changed, 0 insertions, 0 deletions