-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No support for PCIe switches when booted with ACPI #52
Labels
devinfo/acpi
ACPI-related request
status/fix-partial
Issue fixed partially
type/bug
Something isn't working
Comments
Another thing to consider is the Arm DEN0115A spec which describes implementing config space accessors exposed through SMC (so that's ATF territory). Linux had refused supporting this, but I've heard it's supported in ESXi and some BSD variants. |
mariobalanica
added
type/bug
Something isn't working
devinfo/acpi
ACPI-related request
labels
Jul 28, 2023
For Windows and Linux: 4b915e6 There's the PCI SMC left to be implemented in TF-A for BSDs and ESXi. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
devinfo/acpi
ACPI-related request
status/fix-partial
Issue fixed partially
type/bug
Something isn't working
Need to investigate and see what workarounds are available in each OS.
At quick glance, Linux does have custom ECAM accessors for Synquacer and Armada. Can this bind to ACPI somehow?
Windows overall support is still a big question mark due to other unknown issues, but it is actually possible to expose both the root port and full config space via separate MCFG entries on the same segment, with "NXPMX6" set as OEMID for FADT. The only drawback seems to be that this forces BAR space allocations to happen in the 32-bit MMIO window, which is much smaller.
The text was updated successfully, but these errors were encountered: