Re: native vs acpi support

Re: native vs acpi support

[Greg KH]

On Mon, Sep 12, 2005 at 08:16:49AM +0100, vidyut karan wrote:
> Hi all,
>  
> I am a newbie to this hotplug support in linux (specially for
> pci-express). At present i am trying to understand the basics.  While
> reading the hot-plug support for pci-express, I couldn't understand
> the following:
> What is the difference betwwen an
> OS with an "native hot plug support" 
> and controlling the hot-plug by using ACPI.
> Does linux support both these mechanism.

Yes.

My question to you is, what are you trying to do?

Also the pci hotplug mailing list might be the best place for questions
like this.

thanks,

greg k-h


-------------------------------------------------------
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

Re: [ACPI] native vs acpi support

[Rajesh Shah]

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

Re: [ACPI] native vs acpi support

[Rajesh Shah]

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

Re: problem in allocating resources for

[Rajesh Shah]

On Wed, Sep 28, 2005 at 03:08:14PM +0100, vidyut karan wrote:
> 
>    While  inserting  pciehp.ko  module(for  native  hot  plug PCI Express
>    support, ACPI enabled), the following messages appear:
> 
>    "pciehp: pciehp: controller initialization failed".
> 
>    Can somebody give me some pointers where the problem possibly lies.
> 
Please provide the full dmesg output, preferably with pciehp_debug
set to 1. Most of the time I've seen the error happen on systems
that don't support native pci express hotplug.

Rajesh


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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