Re: [acpi-jp 2706] Re: Odd ACPI behavior
On Mon, 29 Sep 2003, Nate Lawson wrote: On Mon, 29 Sep 2003, Kevin Oberman wrote: ACPI attaches the bus twice. See sys/dev/acpica/acpi.c: Thanks. That explains why I get the message twice, but why do I get it at all when the device is disabled in the device.hints file? Dunno. That's probably an sio(4) problem. It does that on my laptop also. It would be a layering violation for sio(4) to even look at the disabled flag. However, it has to look at this flag for consoles, since new-bus is is not initialized when consoles are attached. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [acpi-jp 2706] Re: Odd ACPI behavior
On Mon, 29 Sep 2003, Kevin Oberman wrote: Date: Mon, 29 Sep 2003 13:33:06 -0700 (PDT) From: Nate Lawson [EMAIL PROTECTED] ACPI attaches the bus twice. See sys/dev/acpica/acpi.c: /* * Scan all of the child devices we have created and let them probe/attach. */ ACPI_DEBUG_PRINT((ACPI_DB_OBJECTS, first bus_generic_attach\n)); bus_generic_attach(bus); /* * Some of these children may have attached others as part of their attach * process (eg. the root PCI bus driver), so rescan. */ ACPI_DEBUG_PRINT((ACPI_DB_OBJECTS, second bus_generic_attach\n)); bus_generic_attach(bus); Thanks. That explains why I get the message twice, but why do I get it at all when the device is disabled in the device.hints file? Dunno. That's probably an sio(4) problem. It does that on my laptop also. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
