From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 11 19:13:30 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64ED616A500 for ; Tue, 11 Jul 2006 19:13:30 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D81943D72 for ; Tue, 11 Jul 2006 19:13:28 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 12293 invoked from network); 11 Jul 2006 19:13:26 -0000 Received: from unknown (HELO localhost) (775067@[217.50.132.149]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 11 Jul 2006 19:13:26 -0000 Date: Tue, 11 Jul 2006 21:13:09 +0200 From: Fabian Keil Cc: freebsd-acpi@freebsd.org 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> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_NKDNm2vxTxG6rDoQodmWnk8; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Re: Selectively disabling acpi sub-systems X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 19:13:30 -0000 --Sig_NKDNm2vxTxG6rDoQodmWnk8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable John Baldwin wrote: > On Tuesday 11 July 2006 02:59, M. Warner Losh wrote: > > In message: <20060710143810.61705f74@localhost> > > Fabian Keil 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--