linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: vidyut karan <kvidyut2000@yahoo.co.in>
Cc: Rajesh Shah <rajesh.shah@intel.com>,
	linux-hotplug-devel@lists.sourceforge.net,
	acpi-devel@lists.sourceforge.net, greg@kroah.com
Subject: Re: [ACPI] native vs acpi support
Date: Mon, 26 Sep 2005 17:03:14 +0000	[thread overview]
Message-ID: <20050926100312.B3471@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050924021044.61508.qmail@web35415.mail.mud.yahoo.com>; from kvidyut2000@yahoo.co.in on Sat, Sep 24, 2005 at 03:10:44AM +0100

On Sat, Sep 24, 2005 at 03:10:44AM +0100, vidyut karan wrote:
> 
>    Section [6.7.8] of pci express specs related to OSHP says that
> 
>    "Some  systems  that  include Hot-Plug capable Root Ports and Switches
>    that  are released before ACPI-compliant operating systems with native
>    Hot-Plug support are available, can use ACPI 
>    firmware  for  propagating  Hot-Plug  events.  Firmware control of the
>    Hot-Plug registers must be disabled if an operating system with native
>    support  is  used.  Platforms  that provide ACPI firmware to propagate
>    Hot-Plug events must also provide a control method to transfer control
>    to the operating system."
> 
The _OSC/OSHP mechanism is there to allow a system to support
hotplug on a variety of OS's, some with and some without native
pcie hotplug capabilities. Firmware could boot with the assumption
that it will control hotplug hardware and the OS will only support
the older acpiphp way of doing hot-plug. Of course, this still
requires acpiphp support in the OS. If the system ends up booting
a version of OS that supports native pcie hotplug, it will run the
OSHP method to tell the BIOS that the OS will now control hotplug
hardware directly. After OSHP is run, the BIOS must not attempt to
control hotplug hardware, and must not generate an ACPI interrupt
when hotplug occurs.

>    
>    I  could  not  understand the above properly.Please help me understand
>    this.  If  a OS is not ACPI compliant will it still be able to use the
>    OSHP  method  provided by ACPI. 

No.

> Or does it mean that ACPI will disable
>    the  firmware  taking  control of Hot plug so that OS can take care of
>    that.
> 
Yes.

> 
>    Also in the native hotpluggin on PCI-Express how the control flows for
>    ACPI and non-ACPI case. For e.g. in linux 2.6.
> 
acpi interrupts are not generated any more for hotplug once native
pcie hotplug is enabled. 

Rajesh


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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

  parent reply	other threads:[~2005-09-26 17:03 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 ` [ACPI] " Rajesh Shah
     [not found]   ` <20050924021044.61508.qmail@web35415.mail.mud.yahoo.com>
2005-09-26 17:03     ` Rajesh Shah [this message]
     [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=20050926100312.B3471@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).