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

On Wed, Nov 22, 2006 at 09:39:19PM +0100, Manuel Bouyer wrote:
> On Wed, Nov 22, 2006 at 03:31:02PM +0100, Quentin Garnier wrote:
> > On Wed, Nov 22, 2006 at 12:50:06PM +0100, Manuel Bouyer wrote:
> > > On Wed, Nov 22, 2006 at 12:46:44PM +0100, Quentin Garnier wrote:
> > > >=20
> > > > There is one issue:  disabling the acpi device through boot -c does=
n't
> > > > entirely skip ACPI processing.  acpi_probe() is still called, which=
 does
> > > > execute AML code (going through all the _INI methods).  As a conseq=
uence,
> > > > mpacpi_scan_apics() might be called too.
> > >=20
> > > Is this an issue if we disable ioapic too via boot -c ?
> >=20
> > Not for mpacpi_scan_apics (although cpu devices will be attached
> > according to the MADT).
> >=20
> > But initialising all ACPI objects might be an issue.
>=20
> Hum. Is there a way to detect if acpi has been disabled via boot -c ?

Yes.  I'll think about it to find the easiest way.  It could make a
useful autoconf(9) API.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

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

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

iQEVAwUBRWTi1NgoQloHrPnoAQLCygf/Z2wf/tZ/UpTddur2rd6rb2xnQ1zhfvdZ
fhp6keqZNJWYHvTSDbqekt689ib+pTi3WpUGSzY06IrmxZ2Bcauy1ps7RhpmToEJ
g+GrcXBeYA/eSFpWX06SDdiFTOKSXgYmPgxAhcON6M9YTrhQsc9ykWu7N+iHigcu
WXtIZopdcFfDrpylgOUJXvhLaUWZU4v3UOUIzu+R+Q0hgyzcsboPQngyM29ndUIs
SGY/5bgg9i9T0orvmspvW5JQxx0I7n7HL+pGTnT5OZesPWUug8WIUSE4XygLzHqb
uQJ2lmsXBtR9yyDF53ZxdeEuAme73OoTH3tfuYOMj2fGogde2KSK8Q==
=WnVq
-----END PGP SIGNATURE-----

--e9ndEBTQFD7P4kUb--