Date: Tue, 11 Jul 2006 21:13:09 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: freebsd-acpi@freebsd.org Subject: Re: Selectively disabling acpi sub-systems Message-ID: <20060711211309.3f327a41@localhost> In-Reply-To: <200607110950.19841.jhb@freebsd.org> References: <20060710143810.61705f74@localhost> <20060711.005945.-1962671777.imp@bsdimp.com> <200607110950.19841.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_NKDNm2vxTxG6rDoQodmWnk8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable John Baldwin <jhb@freebsd.org> wrote: > On Tuesday 11 July 2006 02:59, M. Warner Losh wrote: > > In message: <20060710143810.61705f74@localhost> > > Fabian Keil <freebsd-listen@fabiankeil.de> writes: > > : Could someone please tell me how to stop acpi0 from > > : grabbing sio0, without affecting fxp0? > >=20 > > Hack sio not to have a acpi attachment. Or wait for some work that > > we're doing in current to be MFC'd :-) >=20 > That still wouldn't help in his case. :) Probably fxp0's interrupt routi= ng is=20 > busted in the non-ACPI case and to get ACPI to route PCI interrupts you n= eed=20 > to have ACPI probe the device tree which would cause sio0 to be enumerate= d=20 > via ACPI. I only found one ACPI reference in sio and commenting it out did indeed change nothing. I don't have any ideas left for RELENG_6 and will jump to current tomorrow to try my luck there. Fabian --=20 http://www.fabiankeil.de/ --Sig_NKDNm2vxTxG6rDoQodmWnk8 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEs/hUjV8GA4rMKUQRAjEfAKDMZcMX/Almc3exJBsnhNuWzCx/aQCg3kiW IjciY5ZfIwlY4nGIJDlCzr4= =E2Xx -----END PGP SIGNATURE----- --Sig_NKDNm2vxTxG6rDoQodmWnk8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060711211309.3f327a41>