resource_allocator_v4: Fix size of I/O hole at 0x3b0
Addressing comment from CB:41443 that was received after the change landed. memranges_create_hole() takes size as the last parameter. So, the I/O hole created at 0x3b0 needs to set size as 0x3df - 0x3b0 + 1 as 0x3df is the upper limit of that hole. Change-Id: I08fca283436924427e12c6c69edced7e51db42a9 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/41737 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Nico Huber <nico.h@gmx.de> Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
55c735a417
commit
563e614bcd
|
@ -330,7 +330,7 @@ static void constrain_domain_resources(const struct device *domain, struct memra
|
|||
* Don't allow allocations in the VGA I/O range. PCI has special cases for
|
||||
* that.
|
||||
*/
|
||||
memranges_create_hole(ranges, 0x3b0, 0x3df);
|
||||
memranges_create_hole(ranges, 0x3b0, 0x3df - 0x3b0 + 1);
|
||||
|
||||
/*
|
||||
* Resource allocator no longer supports the legacy behavior where I/O resource
|
||||
|
|
Loading…
Reference in New Issue