Gentoo Archives: gentoo-user

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: Questions about SATA and hot plugging.
Date: Wed, 15 Dec 2010 21:04:49
Message-Id: AANLkTink9Z+=9qB-eWhFaNTxmteC1nAJE1aAc-nO-hpw@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: Questions about SATA and hot plugging. by Volker Armin Hemmann
1 On Wed, Dec 15, 2010 at 12:07 PM, Volker Armin Hemmann
2 <volkerarmin@××××××××××.com> wrote:
3 <SNIP>
4 >>
5 >> The logic and timing of the signals on SATA and eSATA cables is
6 >> (TTBOMK) intended to be identical. What those signals look like at
7 >> different places in the cable chain will be different.
8 >>
9 >> - Mark
10 >
11 > and you have sources to support that claims and did not just make it up.
12 >
13 >
14
15 Ouch! Man, you like to put people in their place, don't you! :-)
16
17
18 How about:
19
20 http://www.serialata.org/technology/why_sata.asp
21 http://www.serialata.org/technology/esata.asp
22
23 Wikipedia is an interesting place to go for information but the
24 organization that is responsible for the spec itself is better.
25
26 SATA is currently defined as supporting up to 6Gb/S (now Gen3) while
27 eSATA supports up to 1.5Gb/S (Gen1) or 3Gb/S (Gen2). Internal cables
28 have highly limited lengths. External cables can be much longer. (2
29 meters)
30
31 TTBOMK no one on this list is using a single drive that would exceed
32 1.5Gb/S (roughly 187MB/S) so it's unlikely anyone would see a
33 difference in speed, but that doesn't mean the specs are the same.
34
35 The 'logic' of what's on the cable during data transferred is
36 identical. The _rate_ at which it's transferred on eSATA is slower and
37 the electrical levels are modified to provide more reliability across
38 longer cables and reflections at cable/connector boundaries.
39
40 I trust that you can read the Serial-ATA org web site yourself to get
41 properly educated on the matter.
42
43 Cheers,
44 Mark

Replies

Subject Author
Re: [gentoo-user] Re: Questions about SATA and hot plugging. Volker Armin Hemmann <volkerarmin@××××××××××.com>