From: Mark Lord <liml@rtr.ca>
To: IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Anyone else out there have an ExpressCard to try?
Date: Wed, 17 Oct 2007 12:04:14 -0400 [thread overview]
Message-ID: <4716327E.40903@rtr.ca> (raw)
I have a Dell Inspiron 9400 with an external ExpressCard slot.
I've also got a "Bytecc" 2-port eSATA ExpressCard-34 that identifies as:
Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
To get it to work with Linux on my Dell notebook,
the pcihp_force=1 parameter is necessary for the pciehp module.
After that, it works great with libata and NCQ, of course,
with R/W performance in the 40-60 Mbyte/sec range (depends upon the drive).
Much better than with USB2 (28-30 Mbyte/sec).
The problems are with PCIe hotplug.
If the card is inserted prior to loading pci_hotplug + pciehp modules,
then it is not detected upon modprobe of those modules.
Removing and reinserting the card cures that.
After a suspend/resume (RAM) cycle, card insertion/removal is no longer
detected by pciehp, until doing: rmmod pciehp; modprobe pciehp
Apparently many (all?) Dell notebooks have this problem,
because the ACPI BIOS lacks info/whatever for the ExpressCard slot.
I'm wondering if other brands (or other Dells, even) have similar issues.
So.. if you have one and ExpressCard slot and an ExpressCard,
could you please try testing the above scenarios, and post a reply?
In the reply, describe what works, what doesn't,
and whether or not the pciehp=force parameter was required.
On LKML, there is a patchset to fix the above issues,
and if you have those problems then please try the patches
and report back on that as well.
http://lkml.org/lkml/2007/10/16/465
Thanks.
reply other threads:[~2007-10-17 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4716327E.40903@rtr.ca \
--to=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).