Re: dmesg differences GENERIC/XEN3_DOM0

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Sat, Feb 27, 2021 at 02:59:28PM -0500, Greg%s1.lexort.com@localhost wrote:
> 
> Of course some differences are expected.  But some seem surprising:
> 
>   -agp0 at pchb0: G4X-family chipset
>   -agp0: detected 32252k stolen memory
>   -agp0: aperture at 0xd0000000, size 0x10000000
>   -i915drmkms0 at pci0 dev 2 function 0: Intel 82G45 Integrated Graphics Device (rev. 0x03)
>   -Intel product 2e23 (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured
>   +agp at pchb0 not configured
>   +vga0 at pci0 dev 2 function 0: vendor 8086 product 2e22 (rev. 0x03)
>   +wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
>   +wsmux1: connecting to wsdisplay0
>   +drm at vga0 not configured
>   +vendor 8086 product 2e23 (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured
> 
> Also, even when things are found they print differently:
> 
>   -ahcisata0 at pci0 dev 31 function 2: Intel 82801JI SATA Controller (AHCI mode) (rev. 0x00)
>   +ahcisata0 at pci0 dev 31 function 2: vendor 8086 product 3a22 (rev. 0x00)
> 
> 
> So, is it a goal that XEN3_DOM0 should in general aupport all drivers in
> GENERIC, in the sense that absent a good reason for DOM0 to differ, the
> same hardware is found?  Or is there an articulated plan for
> differences?
> 
> 
> Perhaps put another way, if I were to fix this by making XEN3_DOM0 more
> like GENERIC, would that upset anyone?

adding agp will certainly make the dom0 kernel panic on some hardware.
I removed it for this reason.

for PCIVERBOSE I don't care.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--