From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 12 22:41:55 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 1058916A4E0 for ; Wed, 12 Jul 2006 22:41:55 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8319743D49 for ; Wed, 12 Jul 2006 22:41:54 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k6CMfrEs001260 for ; Wed, 12 Jul 2006 18:41:54 -0400 X-ORBL: [67.119.74.222] Received: from [10.0.0.53] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by pimout7-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k6CMfpPj139442; Wed, 12 Jul 2006 18:41:52 -0400 Message-ID: <44B57AA1.6080604@root.org> Date: Wed, 12 Jul 2006 15:41:37 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Fabian Keil References: <20060710143810.61705f74@localhost> <20060711.005945.-1962671777.imp@bsdimp.com> <200607110950.19841.jhb@freebsd.org> <20060711211309.3f327a41@localhost> In-Reply-To: <20060711211309.3f327a41@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org 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: Wed, 12 Jul 2006 22:41:55 -0000 Fabian Keil wrote: > 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? >>> >>> 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. > > 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. ACPI doesn't change much for sio devices. It's basically ISA with the resource being provided by the _CRS value in the AML (instead of by /boot/*.hints). -- Nate