--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi folks,

The world is not an i386, hopefully, therefore the definitions for
PCI_INTR_FIXUP and friends have to move away from files.i386.  That
might seem surprising, but amd64 uses ACPI, too.

Now, I'm wondering about a few things on that issue:

1.  Will ACPI stay x86-specific?  In other words, should the definitions
    move to files.x86 or files.pci?

2.  PCI_*_FIXUP might makes sense on other archs to solve similar issues,
    after all they have a rather generic name.  files.pci, then?

3.  Why bother making it optional?  Does it break things when it has
    nothing to fix?

Also, while I'm here, I think the pchb and pcib devices from i386/pci/
should move to x86/pci:  EM64T computers will need them.

Comments?  Meanwhile I'll do the quick fix and move the definitions to
files.x86.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--FL5UXtIhxfXey3p5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQsfXWtgoQloHrPnoAQKC8QgAyQJJ0sPsV9hpOh84k9F+HhNI5J9EgWB/
QJqznmRT/uFW+soc2BRcRcygH4RUhX0IZChJWO6Zg7BgLQlrQlLjIxcmxPD4wfG6
fBpnIUZQS80ewYJTGoTrl2gG0VVtB/T0e6UPHtcVRsHzX8dCrxWdSFP3xc7ZHoNp
3+et7tIIZ0zAuNZGWPwqwwz5zWMSbo9TZhFSvXTP3M48DWlL2+gPkGXnMEIYjD+/
U9HJ+Uv/firpcjCqSuhxsiuqLMM8uAEkqrdhXuscERMqzjJ+Q7fqIqVA8d9BvCRC
7BFgkcQUvCFte9QQwSElRITujnIWXPISt9UWk0VqsYm7+FEV1u3xIA==
=znCD
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--