From: Mark Lord <kernel@teksavvy.com>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Support for dual-drive pmp? 0x197b:0x2352
Date: Thu, 19 May 2011 11:53:34 -0400 [thread overview]
Message-ID: <4DD53CFE.9020801@teksavvy.com> (raw)
In-Reply-To: <20110519093948.GB627@htj.dyndns.org>
On 11-05-19 05:39 AM, Tejun Heo wrote:
> Hello, Mark.
>
> On Wed, May 18, 2011 at 03:07:26PM -0400, Mark Lord wrote:
>> But it also fails equally well without the patch. :)
>
> Awesome! :)
>
>> The eSATA host controller is the ever-popular JMicron:
>>
>> 04:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA
>> Controller (rev 02)
>> (197b:2363)
>>
>> Just about everything around here has one of those JMicron chips
>> for the eSATA ports, so I'm guessing that this problem may be
>> somewhat more widespread than just my home office.
>
> Can you send me a link of the PMP device?
Here's the URL. It's a dual-bay eSATA/USB2 dock.
I use these all over the place, with fans added on (by me):
ncix.com/products/?sku=36051
>> So what next?
>> I suspect something isn't quite right in the JMicron AHCI driver code.
>
> I have no idea. I'll get one and see what's up with it.
Thanks!
Whatever the chip inside is, it is reasonably clever:
1. With just a single drive installed, it shows up
as a single-drive, not a PMP.
2. With two drives installed, it enumerates as a PMP.
3. When used over USB2 instead of eSATA, it shows up as a single dev with two LUNs,
rather than as a USB-hub with two devices. Fine by me. :)
4. Spins down the drives when the USB cable is detached (or host sleeps).
Cheers
prev parent reply other threads:[~2011-05-19 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 19:07 Support for dual-drive pmp? 0x197b:0x2352 Mark Lord
2011-05-19 9:39 ` Tejun Heo
2011-05-19 15:53 ` Mark Lord [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=4DD53CFE.9020801@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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).