public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Drivers For USB HDD
Date: Mon, 7 May 2012 16:45:02 -0500	[thread overview]
Message-ID: <CAEH5T2Oe1ztH2AXP7Q87F0D56_6rvJ2Pm9BNiWw94SqD1TZiuQ@mail.gmail.com> (raw)
In-Reply-To: <523B48F0E3404A6E8DCE0D6FAAD6D780@mic2>

On Mon, May 7, 2012 at 4:18 PM, Michael Scherer
<a6702894@unet.univie.ac.at> wrote:
>> On Mon, May 7, 2012 at 8:21 AM, Paul Hartman
>> <paul.hartman+gentoo@gmail.com> wrote:
>>>
>>> On Mon, May 7, 2012 at 10:00 AM, Mark Knecht <markknecht@gmail.com>
>>> wrote:
>>>>
>>>> here are 3 or now I
>>>> think 4 different USB specs - EHCI, OHCI, UHCI, and then whatever USB
>>>> 3.0 is using
>>>
>>>
>>> XHCI
>>>
>>> Furthermore, USB 3.0 has 9-pin ports and cables (for type-A) versus
>>> the 4-pin of USB 1/2. The USB 3.0 sockets are backward-compatible with
>>> older USB devices and cables, but older USB cables are not
>>> forward-compatible with USB 3.0.
>>>
>>
>> Good point. None of my USB 2.0 drives work in my USB 3.0 port. I do
>> have a USB 3.0 drivers, supposedly, and one drive that claims to be
>> eSata/USB 3.0 compatible, but I've not tried to get it working using
>> USB 3.0.
>>
>> - Mark
>>
>>
>

> Seems this either a typo, or a contradiction:
> "The USB 3.0 sockets are backward-compatible with older ... cables"
> would mean I can use the old cables for 3.0, but then
>
> "but older USB cables are not forward-compatible with USB 3.0"
> says I can NOT use the old cables.
> I have no 3.0, but some day I probably will, so I'd like to know what
> exactly you mean.
>
> kind regards
>
> michael

Hi,

Here is what I mean:

USB 3.0 socket is backwards compatible = USB 2.0 cable and devices
still work as USB 2.0 when plugged into USB 3.0 port.

USB 2.0 cable is not forward-compatible = you can not use USB 2.0
cable with USB 3.0 device as USB 3.0. It will only behave as USB 2.0
in that case.

If you want to truly use USB 3.0 you need to have all three: USB 3.0
port, USB 3.0 cable, USB 3.0 device.



  parent reply	other threads:[~2012-05-08  0:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 18:29 [gentoo-amd64] Drivers For USB HDD Frank Peters
2012-05-06 19:18 ` Stan Sander
2012-05-06 22:12   ` Frank Peters
2012-05-06 23:46 ` Paul Hartman
2012-05-07 10:51 ` Thomas Rösner
2012-05-07 13:34   ` Frank Peters
     [not found]     ` <CAK2H+edzy3S9fX86frKLEvYfLN1_dg03k5B3z7DfATbF501S_A@mail.gmail.com>
2012-05-07 15:21       ` Paul Hartman
2012-05-07 15:43         ` Mark Knecht
2012-05-07 21:18           ` Michael Scherer
2012-05-07 21:42             ` Mark Knecht
2012-05-07 21:45             ` Paul Hartman [this message]
2012-05-07 21:58               ` Michael Scherer
2012-05-08 10:56                 ` Thomas Rösner
2012-05-10  2:49     ` Frank Peters
2012-05-10 13:07       ` Benny Pedersen
2012-05-10 15:30         ` Sylvain Alain
2012-05-10 15:42         ` Frank Peters
2012-05-10 16:31           ` Lie Ryan
2012-05-10 16:46             ` Bob Sanders
2012-05-11  0:22             ` [gentoo-amd64] " Duncan
2012-05-11  8:33             ` [gentoo-amd64] " Alex Alexander
2012-05-11 11:20               ` Rich Freeman
2012-05-07 11:31 ` David Relson

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=CAEH5T2Oe1ztH2AXP7Q87F0D56_6rvJ2Pm9BNiWw94SqD1TZiuQ@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.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