From: Mark Lord <kernel@teksavvy.com>
To: Tejun Heo <tj@kernel.org>
Cc: Steven Haigh <netwiz@crc.id.au>,
linux-ide@vger.kernel.org, justin@jmicron.com
Subject: Re: sata-sil drive detection issues.
Date: Thu, 24 Feb 2011 11:21:47 -0500 [thread overview]
Message-ID: <4D66859B.3020806@teksavvy.com> (raw)
In-Reply-To: <20110224100609.GF7840@htj.dyndns.org>
On 11-02-24 05:06 AM, Tejun Heo wrote:
>
>> Near the rear:
>> JMB352 / 0834 LGBA1 A / 370JF3011 - This looks to be hooked up via
>> some capacitors to the DATA data lines on both sockets. If I haven't
>> mentioned before, this is a 2 x SATA drive bay cradle.
>
> This is the SATA part.
>
>> A third tiny chip near the JMB352 is:
>> GL850A / MN2FA01G11 / 911SK03111 - Not 100% sure of the function of
>> this chip by following the tracks, but it looks like it might be
>> some kind of a clock source. That is a wild guess though!
>
> This is USB thingie.
>
> So, the offending part is JMB352. Justin, when JMB352 is doing e-SATA
> interface, it's failing IDENTIFY. sata_sil fails to recognize it and
> ahci (right? Steven) succeeds only after IDENTIFY failures and
> retries. Any ideas what's going on? When doing e-SATA, is the chip
> active or passive? ie. Does it just pass through the signals or do
> some meddling inbetween?
Since this is a dual-SATA device, does it have TWO eSATA ports at the back,
or just one? If the latter, then I'd expect to find a port-multiplier in the chain.
Cheers
next prev parent reply other threads:[~2011-02-24 16:21 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 [this message]
2011-02-24 16:29 ` Steven Haigh
2011-02-24 19:04 ` Mark Lord
2011-02-24 20:26 ` Mark Lord
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=4D66859B.3020806@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.