From: Rajesh Shah <rajesh.shah@intel.com>
To: kylin <fierykylin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-newbie-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-hotplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
dkumar-QByN7dn/BetQWC9lL0RKGQC/G2K4zDHf@public.gmane.org
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Wed, 03 Aug 2005 17:49:43 +0000 [thread overview]
Message-ID: <20050803104940.A3754@unix-os.sc.intel.com> (raw)
In-Reply-To: <87ab37ab0507300920570b0ea6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>; from fierykylin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org on Sun, Jul 31, 2005 at 12:20:30AM +0800
On Sun, Jul 31, 2005 at 12:20:30AM +0800, kylin wrote:
> I wonder if i can workaround the MSI using the polling way on the
> server geared by E7520 and the firmware with no OSC implemented
>
Per the PCI firmware spec (I'm looking at draft 0.9, version 3.0),
the OS must explicitly get control of native pcie hotplug from
firmware using _OSC before trying to use it. Firmware may be
deliberately not creating an _OSC because it is controlling the
hotplug hardware, or may be aware of other reasons (e.g. errata)
why OS native pcie hotplug should not be used on this platform.
So no, I don't think we can load and use pciehp if there's
no _OSC implemented in firmware.
Rajesh
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-08-03 17:49 UTC|newest]
Thread overview: 8+ 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
[not found] ` <b115cb5f0507241949da02aa7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-27 18:29 ` Kristen Accardi
2005-07-28 10:45 ` Rajat Jain
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 10:23 ` Rajat Jain
2005-07-30 16:20 ` kylin
[not found] ` <87ab37ab0507300920570b0ea6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-08-03 17:49 ` Rajesh Shah [this message]
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=20050803104940.A3754@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dkumar-QByN7dn/BetQWC9lL0RKGQC/G2K4zDHf@public.gmane.org \
--cc=fierykylin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-hotplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-newbie-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).