| commit | 563e614bcde9627b764445dfe2fe7cfca7e99c96 | |
| author | Furquan Shaikh <furquan@google.com> | |
| Tue, 26 May 2020 19:04:35 +0000 (26 12:04 -0700) | ||
| committer | Furquan Shaikh <furquan@google.com> | |
| Wed, 27 May 2020 18:57:17 +0000 (27 18:57 +0000) | ||
| tree | 61017088416443c1ff716801550f0d055f5c98d1 | treesnapshot (tar.gz zip) |
| parent | 55c735a417e75387e988553f9f66d27e19f2364b | commitdiff |
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>
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>
| src/device/resource_allocator_v4.c | diffblobblamehistory |