David Woodhouse wrote:
>
> jgarzik@mandrakesoft.com said:
> > Just for paranoia's sake it seems like a good idea to -not- share the
> > ACPI interrupt with anyone else, since it is often tied to core system
> > management functions. Much more so than the USB IRQ at any rate :)
>
> With ACPI enabled in the BIOS...
> With CONFIG_ACPI disabled, USB ends up on IRQ 19 and works.
>
> With CONFIG_ACPI enabled, USB doesn't try to share IRQ 9 with ACPI -
> it ends up on IRQ 10, but doesn't ever receive any interrupts.
> Kernel says on bootup: ACPI: "ABIT" found at 0x000f7550
>
> acpid says S5 not supported, as I said before.
ACPI tables suck
> With ACPI disabled in the BIOS:
> With CONFIG_ACPI disabled, USB ends up on IRQ19 and works.
>
> With CONFIG_ACPI enabled, USB is on IRQ10 and doesn't get IRQs
> Kernel says on bootup: ACPI: found PIIX4 at 0x4000
>
> acpid: started
> acpid: FACP @ 0x012d3400
> acpid: DSDT @ 0x00000000
> acpid: cannot map FACP
Ok you have basic ACPI system support but since ACPI is disabled there
isn't much other knowledge about your system that can be gleaned.
This just makes me itch to write a "native" power management driver for
PIIX4, and do things properly. :/
-- Jeff Garzik | Rule 1: Building 1024 | There is no cabal. MandrakeSoft, Inc. |- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Mar 07 2000 - 21:00:09 EST