On Wednesday 19 April 2006 00:34, Kenji Kaneshige wrote:
> I have a question. The ACPI container driver can be build as a
> kernel module. Should _OSI("Module Device") returns TRUE even
> when container driver module is not loaded? (Typically, _OSI is
> evaluated at _INI time, I think. So container driver module is
> not loaded at _OSI("Module Device") time anyway.)
Good question. I think _OSI("Module Device") should return
true even if the container driver isn't loaded.
Do you think that's a bad idea?
I think it's OK if the namespace contains container devices
that we ignore until the driver is loaded. Someday, the
presence of those devices should be enough to cause udev
to load the driver automatically. But for now, I think we
have to do it manually.
> Bjorn Helgaas wrote:
> > Update _OSI strings to report that "Module Device" is supported.
> >
> > This is Linux-specific, so it should be one of the Linux divergences
> > from the Intel ACPI CA.
> >
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@xxxxxx>
> >
> > Index: work-mm5/drivers/acpi/utilities/uteval.c
> > ===================================================================
> > --- work-mm5.orig/drivers/acpi/utilities/uteval.c 2006-04-18 15:31:22.000000000 -0600
> > +++ work-mm5/drivers/acpi/utilities/uteval.c 2006-04-18 15:32:38.000000000 -0600
> > @@ -69,6 +69,9 @@
> > /* Feature Group Strings */
> >
> > "Extended Address Space Descriptor",
> > +#ifdef CONFIG_ACPI_CONTAINER
> > + "Module Device",
> > +#endif
> > };
> >
> > /* Local prototypes */
> > -
> > 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
> >
>
> -
> 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
>
-
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
