On Thu, 2006-06-22 at 10:58 +0900, KAMEZAWA Hiroyuki wrote: > On Wed, 21 Jun 2006 18:37:00 -0700 > keith mannthey <kmannth@xxxxxxxxxx> wrote: > > > > in acpi_bus_driver_init() > > > - driver->ops.add() is called or not > > > - what it retruns > > > > It is called. But that is not the whole story. > > In acpi_bus_driver_init it calls driver->ops.add(device). This ops.add > > is not acpi_memory_device_add. I do get not any printks that I would > > expect from acpi_memory_device_add. > > > > If I print out in acpi_bus_driver_init > > printk(" device_add() about %s\n",acpi_device_name(device)); > > result = driver->ops.add(device); Looks like this motherboard driver always returns 0. I am going see about fixing this driver. -- keith mannthey <kmannth@xxxxxxxxxx> Linux Technology Center IBM - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html