From: Steven Haigh <netwiz@crc.id.au>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata-sil drive detection issues.
Date: Thu, 24 Feb 2011 20:53:15 +1100 [thread overview]
Message-ID: <4D662A8B.5050501@crc.id.au> (raw)
In-Reply-To: <20110224083123.GB7840@htj.dyndns.org>
On 24/02/2011 7:31 PM, Tejun Heo wrote:
> Well, yeah, IDENTIFY failure is still there. Controllers behave
> differently and some may have higher tolerance under certain
> circumstances but the setup just seems quite flimsy for whatever
> reason.
Yeah - I noticed that. These things can never be simple, can they?!
>> Could it just be that the cradle is slow to initialise and therefore
>> the sata_sil adapter gives up before the cradle is actually ready?
>>
>> Following this logic, I tried powering up the cradle before
>> connecting the esata cable. I don't see anything in dmesg connecting
>> the esata cable AFTER the cradle has been powered on. Maybe the
>> cradle disables the esata connection if theres no cable connected on
>> powerup?
>
> Is the cradle an active device or is it just power supply +
> eSATA->SATA gender? Oh, right, you said it also had USB connection,
> so it's an active device. Can you open it up and see which chip is
> there?
Of course I can crack it open - thats what makes life fun!
The top side of the internal PCB is fairly plain with just the SATA
power & data sockets on it and the various USB ports and card sockets on
the front.
On the rear, we have a 30Mhz and a 12Mhz oscillator and 3 main CPU type
chips.
Near the card readers:
GL826 / MX2AE08G08 / 842H35518 - I assume this is the IDE / CF / card IO
chip.
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.
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!
If you need photos, let me know and I'll make some up.
--
Steven Haigh
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
next prev parent reply other threads:[~2011-02-24 9:53 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 [this message]
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
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=4D662A8B.5050501@crc.id.au \
--to=netwiz@crc.id.au \
--cc=linux-ide@vger.kernel.org \
--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.