From: Rajesh Shah <rajesh.shah@intel.com>
To: vidyut karan <kvidyut2000@yahoo.co.in>
Cc: linux-hotplug-devel@lists.sourceforge.net,
acpi-devel@lists.sourceforge.net, greg@kroah.com
Subject: Re: [ACPI] native vs acpi support
Date: Mon, 12 Sep 2005 18:00:25 +0000 [thread overview]
Message-ID: <20050912110025.A15668@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050912071649.22726.qmail@web35406.mail.mud.yahoo.com>; from kvidyut2000@yahoo.co.in on Mon, Sep 12, 2005 at 08:16:49AM +0100
On Mon, Sep 12, 2005 at 08:16:49AM +0100, vidyut karan wrote:
>
> What is the difference betwwen an
>
> OS with an "native hot plug support"
>
An OS that has hotplug support as described in the PCI Express
specification. This is supported by the pciehp driver.
> and controlling the hot-plug by using ACPI.
>
An OS that has hotplug support as described in the ACPI
specification. This is supported by the acpiphp driver.
Native pcie hotplug is newer and better, since it describes a
usage model (e.g. attention buttons, indicators etc.) and
standardizes the programming interface to the hotplug
hardware.
>
> If my query sounds idiotic, give me some pointers so that i can move
> on the right track.
>
See the PCI hotplug specification and PCI Express specification
from the PCI SIG, and the ACPI specification from
http://www.acpi.info/.
Rajesh
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-09-12 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050912071649.22726.qmail@web35406.mail.mud.yahoo.com>
[not found] ` <20050912071649.22726.qmail-R/RehLzVjnOvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-09-12 16:12 ` native vs acpi support Greg KH
2005-09-12 18:00 ` Rajesh Shah [this message]
[not found] ` <20050924021044.61508.qmail@web35415.mail.mud.yahoo.com>
2005-09-26 17:03 ` [ACPI] " Rajesh Shah
[not found] ` <20050928140814.28476.qmail@web35410.mail.mud.yahoo.com>
2005-09-30 18:42 ` problem in allocating resources for Rajesh Shah
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=20050912110025.A15668@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=kvidyut2000@yahoo.co.in \
--cc=linux-hotplug-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).