Damien Zammit, le dim. 21 août 2022 07:00:49 +, a ecrit:
> Rationale: QEMU allocates actual io ports in the 0xc000 - 0xcfff
> range, therefore we still need to allow rump to access these ports,
> in case they are allocated to real pci hardware.
Applied, thanks!
> ---
> debian/patches/machirq
Damien Zammit, le lun. 22 août 2022 06:58:47 +, a ecrit:
> meaning we only care about reserving access to these ioports (c000-cfff)
> on hardware that was created circa 1992-1993, eg 80486 and first pentiums. [1]
> Also, when PCI_CONF2 range is accessed for pci configuration,
> you must use PCI
Samuel,
I found out that PCI_CONF2 access method was deprecated in PCI v2.0,
meaning we only care about reserving access to these ioports (c000-cfff)
on hardware that was created circa 1992-1993, eg 80486 and first pentiums. [1]
Also, when PCI_CONF2 range is accessed for pci configuration,
you mus
Damien Zammit, le dim. 21 août 2022 07:00:49 +, a ecrit:
> diff --git a/debian/patches/machirqdev.diff b/debian/patches/machirqdev.diff
> index 2f74ca619..41894d288 100644
> --- a/debian/patches/machirqdev.diff
> +++ b/debian/patches/machirqdev.diff
BTW, surely this patch and some others could
Damien Zammit, le dim. 21 août 2022 07:00:49 +, a ecrit:
> Rationale: QEMU allocates actual io ports in the 0xc000 - 0xcfff
> range, therefore we still need to allow rump to access these ports,
> in case they are allocated to real pci hardware.
I'm a bit worried to let rump access cfg2 registe
Rationale: QEMU allocates actual io ports in the 0xc000 - 0xcfff
range, therefore we still need to allow rump to access these ports,
in case they are allocated to real pci hardware.
---
debian/patches/machirqdev.diff | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff
