I'm only familiar with the situation on Macs, where all of this happens natively: There's an EFI driver to configure tunnels to devices already attached on boot, and there's an OS driver which takes over after ExitBootServices. ![]() > (not pciehp) to support these Thunderbolt devices? > Is the ACPI Bus Check event that hook? Does that mean we must use acpiphp > things behind the adapter, there must be a hook where firmware gets invoked. > If the firmware is responsible for configuring This is also what Acelan Kao wrote above. ![]() In the dmesg output it can be seen that the adapter was present on boot, then unplugged and replugged. ![]() (In reply to Bjorn Helgaas from comment #2)
0 Comments
Leave a Reply. |