You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The old implementation would resolve this to a device name string which could then be used to look for the _CRS entry on the link device. However, now because it resolves to a Device, a dead end is reached.
When using the 'q35' device, this problem does go away, as that device seems to be what is used to test this implementation, and the reference kind turns into Unresolved which then resolves to a String.
It is important to note that in the current (non-rewritten) ACPI crate, this works as expected. This is just present in the new version.
The text was updated successfully, but these errors were encountered:
I am making this issue for the new ACPI crate rewrite as it seems like that is where things will be going.
Using QEMU / OVMF it is impossible to use the current AML implementation using the 'pc' virtual machine.
When a PCI device wants to specify a link device, when running in 'pc' mode the resolved type is:
The old implementation would resolve this to a device name string which could then be used to look for the _CRS entry on the link device. However, now because it resolves to a Device, a dead end is reached.
When using the 'q35' device, this problem does go away, as that device seems to be what is used to test this implementation, and the reference kind turns into
Unresolved
which then resolves to a String.It is important to note that in the current (non-rewritten) ACPI crate, this works as expected. This is just present in the new version.
The text was updated successfully, but these errors were encountered: