All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristen Accardi <kristen.kml@gmail.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
	linux-newbie@vger.kernel.org, acpi-devel@lists.sourceforge.net,
	linux-hotplug-devel@lists.sourceforge.net,
	dkumar@noida.hcltech.com
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Thu, 28 Jul 2005 10:00:14 -0700	[thread overview]
Message-ID: <512afbf905072810005f327e3@mail.gmail.com> (raw)
In-Reply-To: <b115cb5f05072803451836055c@mail.gmail.com>

On 7/28/05, Rajat Jain <rajat.noida.india@gmail.com> wrote:
> >
> > Hi Rajat, you can learn more about the OSHP method by reading the PCI
> > express spec.  It is used to tell an ACPI bios that the OS will be
> > handling the hotplug events natively.  It may be that your BIOS does
> > not allow native hotplug for pcie, in which case you need to be using
> > the acpiphp driver instead of the pciehp driver.  You could just try
> > modprobing acpiphp and see if this will handle the hotplug events.  A
> > recent version of lspci (which understands pcie) will tell you as well
> > if pcie hotplug capability is supported (lspci -vv).
> >
> 
> Okay. I'm sorry but I'm not very clear with this. I'm just putting
> down here my understanding. So basically we have two mutually
> EXCLUSIVE hotplug drivers I can use for PCI Express:
> 
> 1) "pciehp.ko" : We use this PCIE HP driver when our BIOS supports
> Native Hot-plug for PCI Express (which means that hot-plug will be
> handled by OS single handedly).
> 
> 2) "acpiphp.ko" : We use this "generic" ACPI HP driver when BIOS
> allows only ITSELF to handle hot-plug events.

usually this is configurable.  So, you can configure you BIOS to use
acpi to handle hot-plug, or you can allow the OS to handle it.  Most
OS (from what I hear) don't actually implement native hotplug support,
so native hotplug support is probably not as big a priority for bios
writers as the acpi support.  so, it doesn't surprise me to find some
that don't support native.

you can run the native hotplug driver on a system who's bios supports
acpi - if it provides the OSHP method, this tells the bios to allow
the OS to handle it.

> 
> Is my understanding correct? I would appreciate if you could help me
> gain a grip on this.

i'm trying to gain a grip myself, as i've just started learning about
pcie :).  someone else hopefully will correct me if i'm telling you
the wrong info.


> 
> Thanks a lot for the useful info you gave. Provided me with a new
> direction to work on.
> 
> Regards,
> 
> Rajat
> 

Kristen


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

WARNING: multiple messages have this Message-ID (diff)
From: Kristen Accardi <kristen.kml@gmail.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
	linux-newbie@vger.kernel.org, acpi-devel@lists.sourceforge.net,
	linux-hotplug-devel@lists.sourceforge.net,
	dkumar@noida.hcltech.com
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Thu, 28 Jul 2005 17:00:14 +0000	[thread overview]
Message-ID: <512afbf905072810005f327e3@mail.gmail.com> (raw)
In-Reply-To: <b115cb5f05072803451836055c@mail.gmail.com>

On 7/28/05, Rajat Jain <rajat.noida.india@gmail.com> wrote:
> >
> > Hi Rajat, you can learn more about the OSHP method by reading the PCI
> > express spec.  It is used to tell an ACPI bios that the OS will be
> > handling the hotplug events natively.  It may be that your BIOS does
> > not allow native hotplug for pcie, in which case you need to be using
> > the acpiphp driver instead of the pciehp driver.  You could just try
> > modprobing acpiphp and see if this will handle the hotplug events.  A
> > recent version of lspci (which understands pcie) will tell you as well
> > if pcie hotplug capability is supported (lspci -vv).
> >
> 
> Okay. I'm sorry but I'm not very clear with this. I'm just putting
> down here my understanding. So basically we have two mutually
> EXCLUSIVE hotplug drivers I can use for PCI Express:
> 
> 1) "pciehp.ko" : We use this PCIE HP driver when our BIOS supports
> Native Hot-plug for PCI Express (which means that hot-plug will be
> handled by OS single handedly).
> 
> 2) "acpiphp.ko" : We use this "generic" ACPI HP driver when BIOS
> allows only ITSELF to handle hot-plug events.

usually this is configurable.  So, you can configure you BIOS to use
acpi to handle hot-plug, or you can allow the OS to handle it.  Most
OS (from what I hear) don't actually implement native hotplug support,
so native hotplug support is probably not as big a priority for bios
writers as the acpi support.  so, it doesn't surprise me to find some
that don't support native.

you can run the native hotplug driver on a system who's bios supports
acpi - if it provides the OSHP method, this tells the bios to allow
the OS to handle it.

> 
> Is my understanding correct? I would appreciate if you could help me
> gain a grip on this.

i'm trying to gain a grip myself, as i've just started learning about
pcie :).  someone else hopefully will correct me if i'm telling you
the wrong info.


> 
> Thanks a lot for the useful info you gave. Provided me with a new
> direction to work on.
> 
> Regards,
> 
> Rajat
> 

Kristen


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

WARNING: multiple messages have this Message-ID (diff)
From: Kristen Accardi <kristen.kml@gmail.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
	linux-newbie@vger.kernel.org, acpi-devel@lists.sourceforge.net,
	linux-hotplug-devel@lists.sourceforge.net,
	dkumar@noida.hcltech.com
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Thu, 28 Jul 2005 10:00:14 -0700	[thread overview]
Message-ID: <512afbf905072810005f327e3@mail.gmail.com> (raw)
In-Reply-To: <b115cb5f05072803451836055c@mail.gmail.com>

On 7/28/05, Rajat Jain <rajat.noida.india@gmail.com> wrote:
> >
> > Hi Rajat, you can learn more about the OSHP method by reading the PCI
> > express spec.  It is used to tell an ACPI bios that the OS will be
> > handling the hotplug events natively.  It may be that your BIOS does
> > not allow native hotplug for pcie, in which case you need to be using
> > the acpiphp driver instead of the pciehp driver.  You could just try
> > modprobing acpiphp and see if this will handle the hotplug events.  A
> > recent version of lspci (which understands pcie) will tell you as well
> > if pcie hotplug capability is supported (lspci -vv).
> >
> 
> Okay. I'm sorry but I'm not very clear with this. I'm just putting
> down here my understanding. So basically we have two mutually
> EXCLUSIVE hotplug drivers I can use for PCI Express:
> 
> 1) "pciehp.ko" : We use this PCIE HP driver when our BIOS supports
> Native Hot-plug for PCI Express (which means that hot-plug will be
> handled by OS single handedly).
> 
> 2) "acpiphp.ko" : We use this "generic" ACPI HP driver when BIOS
> allows only ITSELF to handle hot-plug events.

usually this is configurable.  So, you can configure you BIOS to use
acpi to handle hot-plug, or you can allow the OS to handle it.  Most
OS (from what I hear) don't actually implement native hotplug support,
so native hotplug support is probably not as big a priority for bios
writers as the acpi support.  so, it doesn't surprise me to find some
that don't support native.

you can run the native hotplug driver on a system who's bios supports
acpi - if it provides the OSHP method, this tells the bios to allow
the OS to handle it.

> 
> Is my understanding correct? I would appreciate if you could help me
> gain a grip on this.

i'm trying to gain a grip myself, as i've just started learning about
pcie :).  someone else hopefully will correct me if i'm telling you
the wrong info.


> 
> Thanks a lot for the useful info you gave. Provided me with a new
> direction to work on.
> 
> Regards,
> 
> Rajat
> 

Kristen

  reply	other threads:[~2005-07-28 17:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050725021747.67869.qmail@web34405.mail.mud.yahoo.com>
     [not found] ` <20050725021747.67869.qmail-6mNr3ekj/EivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-07-25  2:49   ` Re: Problem while inserting pciehp (PCI Express Hot-plug) driver Rajat Jain
2005-07-25  2:49     ` Rajat Jain
2005-07-25  2:49     ` Rajat Jain
     [not found]     ` <b115cb5f0507241949da02aa7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-27 18:29       ` Kristen Accardi
2005-07-27 18:29         ` Kristen Accardi
2005-07-27 18:29         ` Kristen Accardi
2005-07-28 10:45         ` Rajat Jain
2005-07-28 10:45           ` Rajat Jain
2005-07-28 10:45           ` Rajat Jain
2005-07-28 17:00           ` Kristen Accardi [this message]
2005-07-28 17:00             ` Kristen Accardi
2005-07-28 17:00             ` Kristen Accardi
     [not found]           ` <b115cb5f05072803451836055c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-29  0:52             ` Rajesh Shah
2005-07-29  0:52               ` Rajesh Shah
2005-07-29  0:52               ` Rajesh Shah
2005-07-29 10:23               ` Rajat Jain
2005-07-29 10:23                 ` Rajat Jain
2005-07-29 10:23                 ` Rajat Jain
2005-07-30 16:20 kylin
2005-07-30 16:20 ` kylin
2005-07-30 16:20 ` kylin
     [not found] ` <87ab37ab0507300920570b0ea6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-08-03 17:49   ` Rajesh Shah
2005-08-03 17:49     ` Rajesh Shah
2005-08-03 17:49     ` 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=512afbf905072810005f327e3@mail.gmail.com \
    --to=kristen.kml@gmail.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=dkumar@noida.hcltech.com \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=rajat.noida.india@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.