From: Mark Lord <kernel@teksavvy.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org, justin@jmicron.com
Subject: Re: sata-sil drive detection issues.
Date: Thu, 24 Feb 2011 15:26:55 -0500 [thread overview]
Message-ID: <4D66BF0F.3040907@teksavvy.com> (raw)
In-Reply-To: <4D66ABC6.8030909@teksavvy.com>
On 11-02-24 02:04 PM, Mark Lord wrote:
> On 11-02-24 11:29 AM, Steven Haigh wrote:
>>
>> There is only one eSATA port on the back of the cradle. From looking at the
>> specs of the JMB352[1], it seems that it has the capability to have 3 SATA
>> channels. Two are used for the cradle bays, the third for the uplink to the PC.
>>
>> The PDF states:
>> "The SATA controller could be configured as host or device. The
>> 3-port SATA II 3.0G controllers further supports the eSATA to dual SATA
>> communication."
>>
>> [1] - http://www.jmicron.com/PDF/JMB352/JMB352.pdf
>
>
> It would be nice to know what that actually means.
> The only standard way for a single eSATA to connect to two SATA
> is via a SATA Port Multiplier. I wonder if that chip implements one?
The product brief lists possible operation modes of the chip as:
-- RAID0, RAID1, JBOD, or Port Multiplier
So I would guess that the drive detection issues must have something
to do with the operation mode. I wonder how one selects *which* mode
should be used by the chip?
Or quite likely the only hardware mode is "Port Multiplier",
and the rest are just fakeraid things in software.
You and Tejun ought to be able to collect some debugging info
(eg. initial ATA register state on probe) to see if the device
even tries to report itself as a port multiplier.
Tricky stuff, undocumented hardware.
next prev parent reply other threads:[~2011-02-24 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 3:16 sata-sil drive detection issues Steven Haigh
2011-02-17 4:23 ` Steven Haigh
2011-02-17 9:58 ` Tejun Heo
2011-02-17 23:20 ` Steven Haigh
2011-02-18 9:16 ` Tejun Heo
2011-02-24 2:24 ` Steven Haigh
2011-02-24 8:31 ` Tejun Heo
2011-02-24 9:53 ` Steven Haigh
2011-02-24 10:06 ` Tejun Heo
2011-02-24 16:21 ` Mark Lord
2011-02-24 16:29 ` Steven Haigh
2011-02-24 19:04 ` Mark Lord
2011-02-24 20:26 ` Mark Lord [this message]
2011-02-28 10:07 ` Steven Haigh
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=4D66BF0F.3040907@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=justin@jmicron.com \
--cc=linux-ide@vger.kernel.org \
--cc=netwiz@crc.id.au \
--cc=tj@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).