From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 11 15:02:19 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 D29E316A695 for ; Tue, 11 Jul 2006 15:02:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2E9343D73 for ; Tue, 11 Jul 2006 15:02:13 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6BF1qGb075013; Tue, 11 Jul 2006 11:01:52 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Tue, 11 Jul 2006 09:50:19 -0400 User-Agent: KMail/1.9.1 References: <20060710143810.61705f74@localhost> <20060711.005945.-1962671777.imp@bsdimp.com> In-Reply-To: <20060711.005945.-1962671777.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607110950.19841.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 11 Jul 2006 11:01:58 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1591/Mon Jul 10 15:41:02 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: 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 15:02:19 -0000 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? > > Hack sio not to have a acpi attachment. Or wait for some work that > we're doing in current to be MFC'd :-) That still wouldn't help in his case. :) Probably fxp0's interrupt routing is busted in the non-ACPI case and to get ACPI to route PCI interrupts you need to have ACPI probe the device tree which would cause sio0 to be enumerated via ACPI. -- John Baldwin