From: Rajesh Shah <rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Paul Ionescu <i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI hotplug
Date: Thu, 13 Jan 2005 12:06:45 -0800 [thread overview]
Message-ID: <20050113120644.A911@unix-os.sc.intel.com> (raw)
In-Reply-To: <pan.2005.01.13.14.02.37.561980-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>; from i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org on Thu, Jan 13, 2005 at 03:02:37PM +0100
On Thu, Jan 13, 2005 at 03:02:37PM +0100, Paul Ionescu wrote:
>
> I just read that 2.6.11-rc1 does support ACPI hotplug.
> What does this really mean ?
> I found some new files in /sys/firmware:
> find /sys/firmware/ | grep eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FDC/FDD0/eject
>
The new ACPI code is to support _physical_ insertion/removal of
cpus and "containers" (nodes) that have cpus and memory. This
requires firmware/platform support. Linux already supports ACPI
(as well as SHPC/PCI-Express) based physical insertion/removal of
IO adapters independent of the new code in 2.6.11-rc1. The ACPI
namespace you listed above shows ACPI ejectable IO devices. This
is handled by the existing acpiphp code, not the new processor
or container code.
Rajesh
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-13 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 14:02 ACPI hotplug Paul Ionescu
[not found] ` <pan.2005.01.13.14.02.37.561980-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2005-01-13 20:06 ` Keshavamurthy Anil S
[not found] ` <20050113120620.A1002-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-01-15 10:26 ` Paul Ionescu
2005-01-13 20:06 ` Rajesh Shah [this message]
[not found] ` <20050113120644.A911-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-01-15 10:14 ` Paul Ionescu
[not found] ` <20050115101454.67867.qmail-NMLAVizEvX2A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2005-01-17 22:01 ` Rajesh Shah
[not found] ` <20050117140121.A21143-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-01-17 22:17 ` Paul Ionescu
[not found] ` <20050117221751.49612.qmail-zX69vREatC6A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2005-01-17 23:48 ` Rajesh Shah
[not found] ` <20050117154801.A22139-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-01-18 8:11 ` Paul Ionescu
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 6:53 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD3057501006CA1-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-01-18 7:26 ` Paul Ionescu
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=20050113120644.A911@unix-os.sc.intel.com \
--to=rajesh.shah-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
/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