summaryrefslogtreecommitdiff
path: root/src/mainboard/packardbell
diff options
context:
space:
mode:
authorAngel Pons <th3fanbus@gmail.com>2021-04-02 22:42:53 +0200
committerAngel Pons <th3fanbus@gmail.com>2021-04-05 13:16:22 +0000
commite24f97c081f3e134362081913793d5adb90eddd5 (patch)
tree0d1836ad9473b51ecca07dc2465a736201b08a8a /src/mainboard/packardbell
parent83e319d6f5b4802fdc862f4bcbe830ccb9e4dfa6 (diff)
nb/intel/ironlake: Drop `pci_mmio_size`
There's no good reason to use values smaller than 2 GiB here. Well, it increases available DRAM in 32-bit space. However, as this is a 64-bit platform, it's highly unlikely that 32-bit limitations would cause any issues anymore. It's more likely to have the allocator give up because memory-mapped resources in 32-bit space don't fit within the specified MMIO size, which can easily occur when using a discrete graphics card. Change-Id: I6cdce5f56bc94cca7065ee3e38af60d1de66e45c Signed-off-by: Angel Pons <th3fanbus@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/52070 Reviewed-by: Nico Huber <nico.h@gmx.de> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/packardbell')
-rw-r--r--src/mainboard/packardbell/ms2290/devicetree.cb2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/mainboard/packardbell/ms2290/devicetree.cb b/src/mainboard/packardbell/ms2290/devicetree.cb
index b57b3feba8..d5f96cba6e 100644
--- a/src/mainboard/packardbell/ms2290/devicetree.cb
+++ b/src/mainboard/packardbell/ms2290/devicetree.cb
@@ -24,8 +24,6 @@ chip northbridge/intel/ironlake
end
end
- register "pci_mmio_size" = "2048"
-
device domain 0 on
device pci 00.0 on # Host bridge
subsystemid 0x1025 0x0379