Issue #611 has been updated by Matt DeVillier.
> Maybe you hit a similar issue, but its more obfuscated in your case? In any > case we should update the UEFIPayloadPkg function (hoping nothing else in > EDK2 depends on it) to not assume a continuous MMIO space. I think you may be right. looking at the cbmem and dmesg logs from both the top-down and bottom-up allocations, coreboot allocates the same memory windows: ```[INFO ] DOMAIN: 00000000: Resource ranges: [INFO ] * Base: 80000000, Size: 70000000, Tag: 200 [INFO ] * Base: f4000000, Size: a000000, Tag: 200 [INFO ] * Base: 17f000000, Size: 7e81000000, Tag: 200 ``` but for the 2nd window, the kernel isn't seeing the full size: ``` pci_bus 0000:00: root bus resource [mem 0x80000000-0xefffffff window] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window] ``` I'm guessing edk2 is futzing with the memory map. In the top down scenario, the kernel sees the I2C controllers as being outside of the (incorrectly small) 2nd window, and remaps them inside the first. Windows likely see it and just says sorry, no I2C for you. I'll grab some edk2 logs and see if there's anything insightful there ---------------------------------------- Bug #611: I2C Controllers fail to initialize under Win11 with top-down allocation on pre-FSP 2.0 platforms https://ticket.coreboot.org/issues/611#change-2152 * Author: Matt DeVillier * Status: New * Priority: Normal * Category: coreboot common code * Target version: none * Start date: 2025-10-12 * Affected versions: main ---------------------------------------- When booting Win11 using edk2 payload and top-down resource allocation (which is now the default), pre-FSP 2.0 platforms all seem to have issues with the I2C controllers failing to initialize. Windows Device Manager reports a Code 35 error: Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. Microsoft's support pages provide the following: > Full Error Message > > Your computer's system firmware does not include enough information to > properly configure and use this device. To use this device, contact your > computer manufacturer to obtain a firmware or BIOS update. (Code 35) > > Cause > > The Multiprocessor System (MPS) table, which stores the resource assignments > for the BIOS, is missing an entry for your device and must be updated. > > Recommended Resolution > > Contact the manufacturer of your computer to update the BIOS. compiling with `RESOURCE_ALLOCATION_TOP_DOWN=n` resolves the issue Tested on: google/slippy (HSW) google/auron (BSW) google/rambi (BYT) google/cyan (BSW) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
