From: Mark Lord <lkml@rtr.ca>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: kristen.c.accardi@intel.com, greg@kroah.com,
Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [Pcihpd-discuss] [PATCH 1/3] pciehp: hotplug: deal with pre-inserted ExpressCards
Date: Thu, 18 Oct 2007 09:31:26 -0400 [thread overview]
Message-ID: <4717602E.2080903@rtr.ca> (raw)
In-Reply-To: <47174069.9000108@jp.fujitsu.com>
Kenji Kaneshige wrote:
> Hi Mark,
>
> I still don't understand what the problems is very much.
If a PCIe ExpressCard34 is inserted into the slot *before*
I modprobe pciehp (with pciehp_force=1), then the card is not
detected nor enabled. The patch provided here fixes that.
> Could you give me answers against the following questions?
>
> (1) Did you try "echo 1 > /sys/bus/pci/slots/XXX/power"?
> (XXX is the slot number to which your card had been inserted)
> (2) If the answer against (1) is yes, did "echo 1 > ..." work?
After 1. inserting the card, and then 2. modprobing pciehp,
the value of /sys/bus/pci/slots/XXX/power is already "1".
But, yes, doing "echo 1" into it does trigger card detection
and things work afterwards. This doesn't really help,
because it doesn't happen automatically, unless the kernel patch
is applied.
> (6) I think your slot is surprise removable. Is it correct?
Yes, it's an externally accessible ExpressCard slot on a notebook,
which is intended to be fully hotpluggable by surprise or otherwise.
Cheers
next prev parent reply other threads:[~2007-10-18 13:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 2:57 [PATCH 0/3] Fix two PEIe hotplug issues Mark Lord
2007-10-18 2:59 ` [PATCH 1/3] pciehp_handle_preinserted_card Mark Lord
2007-10-18 3:00 ` [PATCH 2/3] pciehp_split_pcie_init Mark Lord
2007-10-18 3:02 ` [PATCH 3/3] pciehp_resume_reinit_hardware Mark Lord
2007-10-18 3:03 ` [PATCH 1/3] pciehp_handle_preinserted_card Mark Lord
2007-10-18 3:04 ` [PATCH 2/3] pciehp_split_pcie_init Mark Lord
2007-10-18 3:05 ` [PATCH 0/3] Fix two PEIe hotplug issues Mark Lord
2007-10-18 3:09 ` Mark Lord
2007-10-18 16:13 ` Kristen Carlson Accardi
2007-10-18 17:06 ` Mark Lord
2007-10-18 17:06 ` Kristen Carlson Accardi
2007-10-18 17:49 ` Theodore Tso
2007-10-18 17:56 ` Kristen Carlson Accardi
2007-10-18 21:11 ` Mark Lord
2007-10-18 21:26 ` Mark Lord
2007-10-18 3:32 ` [PATCH 1/3] pciehp: hotplug: deal with pre-inserted ExpressCards Mark Lord
2007-10-18 3:33 ` [PATCH 2/3] pciehp: hotplug: split out hardware init from pcie_init() Mark Lord
2007-10-18 3:34 ` [PATCH 3/3] pciehp: hotplug: reinit hotplug h/w on resume from suspend Mark Lord
2007-10-18 11:15 ` [Pcihpd-discuss] [PATCH 1/3] pciehp: hotplug: deal with pre-inserted ExpressCards Kenji Kaneshige
2007-10-18 13:31 ` Mark Lord [this message]
2007-10-19 2:38 ` Kenji Kaneshige
2007-10-19 3:09 ` Mark Lord
2007-10-19 3:27 ` Kenji Kaneshige
2007-11-18 0:27 ` [PATCH] Fix PCIe double initialization bug Mark Lord
2007-11-18 12:23 ` Rafael J. Wysocki
2007-11-18 14:20 ` Mark Lord
2007-11-18 14:37 ` Mark Lord
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=4717602E.2080903@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=tytso@mit.edu \
/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