Date: Wed, 12 Jul 2006 15:41:37 -0700 From: Nate Lawson <nate@root.org> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: freebsd-acpi@freebsd.org Subject: Re: Selectively disabling acpi sub-systems Message-ID: <44B57AA1.6080604@root.org> In-Reply-To: <20060711211309.3f327a41@localhost> References: <20060710143810.61705f74@localhost> <20060711.005945.-1962671777.imp@bsdimp.com> <200607110950.19841.jhb@freebsd.org> <20060711211309.3f327a41@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Fabian Keil wrote: > 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? >>> >>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44B57AA1.6080604>