Acked-by: Peter Grehan <grehan@...>

previous feedback that Bhyve developers > strongly preferred the BhyveFwCtl mechanism. I've been out of the loop > though (busy with $dayjob) so I don't know if things have changed. > Hopefully other

Reviewed-by: Peter Grehan <grehan@...>

UINT64 value to UINT32 value.> > Cc: Rebecca Cran <rebecca@...>> Cc: Peter Grehan <grehan@...>> Signed-off-by: Michael D Kinney <michael.d.kinney@...> Acked-by: Peter Grehan <greha

Yep, that's fair enough. later, Peter.

created ACPI tables provided by OVMF. Instead use the dynamically> created ACPI tables of bhyve. If bhyve provides no ACPI tables or> we are unable to detect those, fall back to OVMF tables. This look

It's not so much a fundamental technical limitation as in a large amount of work in FreeBSD for almost zero return - maybe a fundamental resource limitation. Well versed in those issues :) It creates

Reviewed-by: Peter Grehan <grehan@...>

Reviewed-by: Peter Grehan <grehan@...>

Hi Michael, Only two choices ? :) Maybe half way between those points. later, Peter.

Hi Corvin, Uhci/Ehci only support legacy interrupts and that isn't supported by bhyve PCI passthru. later, Peter.

Hi Corvin, bhyve doesn't (and will likely never) support Uhci/Ehci controllers so those lines can be removed. later, Peter.

Hi Corvin, I have no issue with adding USB support or fixing the PCI32 base: that either codifies existing behaviour or adds functionality. However, flipping the switch over to bus enumeration being i

Reviewed-by: Peter Grehan <grehan@...>

Reviewed-by: Peter Grehan <grehan@...>

Acked by: Peter Grehan <grehan@...>

Reviewed-by: Peter Grehan <grehan@...>

Reviewed-by: Peter Grehan <grehan@...>

Acked-by: Peter Grehan <grehan@...>

Acked-by: Peter Grehan <grehan@...>