From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>, Greg KH <greg@kroah.com>
Subject: Re: USB extension (repeater) cable
Date: Sun, 21 Jan 2007 08:20:19 +0100 [thread overview]
Message-ID: <45B31433.5000408@xs4all.nl> (raw)
In-Reply-To: <45B313AD.7080705@zytor.com>
H. Peter Anvin wrote:
> Greg KH wrote:
>> On Fri, Jan 19, 2007 at 04:40:34PM +0100, Udo van den Heuvel wrote:
>>>
>>> I just tried my shiny new usb extension cable (repeater):
>>>
>>> Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
>>> ehci_hcd and address 60
>>> Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1
>>> choice
>>> Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
>>> Jan 19 16:01:17 epia kernel: hub 5-1:1.0: 4 ports detected
>>> Jan 19 16:01:18 epia kernel: hub 5-1:1.0: Cannot enable port 1. Maybe
>>> the USB cable is bad?
>>> Jan 19 16:01:22 epia last message repeated 3 times
>>> Jan 19 16:01:23 epia kernel: hub 5-1:1.0: Cannot enable port 2. Maybe
>>> the USB cable is bad?
>>> Jan 19 16:01:26 epia last message repeated 3 times
>>> Jan 19 16:01:27 epia kernel: hub 5-1:1.0: Cannot enable port 3. Maybe
>>> the USB cable is bad?
>>> Jan 19 16:01:31 epia last message repeated 3 times
[...]
> Actually, what it looks like is even simpler. The extension cable
> contains a four-port hub chip (which is the most common commodity chip)
> and haven't bothered changing the descriptor to tell the computer only
> one port is actually active. So only one port can be activated, and the
> others are stubbed out in some evil way. In that case, it should be
> noisy but harmless.
I will do some more testing then.
Is there a way to get rid of the messages?
next prev parent reply other threads:[~2007-01-21 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 15:40 USB extension (repeater) cable Udo van den Heuvel
2007-01-20 0:01 ` Greg KH
2007-01-21 7:18 ` H. Peter Anvin
2007-01-21 7:20 ` Udo van den Heuvel [this message]
2007-01-21 7:22 ` H. Peter Anvin
2007-01-21 23:08 ` Sven-Haegar Koch
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=45B31433.5000408@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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