From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
"Moore, Robert" <robert.moore@intel.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>,
Motoyuki Ito <motoyuki@soft.fujitsu.com>
Subject: Re: [2/2] ACPI: report "Module Device" support via _OSI
Date: Thu, 20 Apr 2006 17:33:28 +0900 [thread overview]
Message-ID: <44474758.6000208@jp.fujitsu.com> (raw)
In-Reply-To: <200604191022.05016.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> 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.
>
I see. I think you are right.
But now, I'm wondering why ACPI firmware needs _OSI("Module
Device") because I think module devices in the namespace will
be ignored by the OS if it doesn't support "Module Device"...
Anyway, thank you for your answer.
Thanks,
Kenji Kaneshige
>
>>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@hp.com>
>>>
>>>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@vger.kernel.org
>>>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@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
next prev parent reply other threads:[~2006-04-20 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 21:58 [2/2] ACPI: report "Module Device" support via _OSI Bjorn Helgaas
2006-04-19 6:34 ` Kenji Kaneshige
2006-04-19 16:22 ` Bjorn Helgaas
2006-04-20 8:33 ` Kenji Kaneshige [this message]
2006-04-20 14:42 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 17:23 Moore, Robert
2006-04-21 18:21 ` Bjorn Helgaas
2006-04-21 18:24 Moore, Robert
2006-04-25 7:22 Therien, Guy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44474758.6000208@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=motoyuki@soft.fujitsu.com \
--cc=robert.moore@intel.com \
--cc=tokunaga.keiich@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox