From: Peter Stuge <stuge-linuxbios@cdy.org>
To: linuxbios@linuxbios.org
Cc: Andi Kleen <ak@suse.de>,
linux-usb-devel@lists.sourceforge.net, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: Re: [LinuxBIOS] [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support.
Date: Thu, 7 Dec 2006 10:51:16 +0100 [thread overview]
Message-ID: <20061207095116.27665.qmail@cdy.org> (raw)
In-Reply-To: <5986589C150B2F49A46483AC44C7BCA4907291@ssvlexmb2.amd.com>
On Wed, Dec 06, 2006 at 01:08:14PM -0800, Lu, Yinghai wrote:
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Wednesday, December 06, 2006 12:59 PM
>
> >I haven't looked how the other usb_debug works -- if it's polled
> >too then it wouldn't have much advantage.
>
> Need to verify if the two sides of debug cable are identical.
I got my device yesterday and after a small plugfest I can confirm
that only one end of the device enumerates when connected to an ICH7
EHCI driven by 2.6.19.
--8<--
Bus 001 Device 027: ID 0525:127a Netchip Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0525 Netchip Technology, Inc.
idProduct 0x127a
bcdDevice 1.01
iManufacturer 1 NetChip
iProduct 2 NetChip TurboCONNECT 2.0
iSerial 3 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Debug descriptor:
bLength 4
bDescriptorType 10
bDebugInEndpoint 0x82
bDebugOutEndpoint 0x01
-->8--
The device is in fact not self-powered.
My theory is that the same set of descriptors are used for both ends,
but one end has been locked to address 127 in order to work with
simpler debug port drivers that assume it will be there.
I guess that the self-powered error is also to simplify life for
debug port drivers. IIRC most if not all USB power management
concerns are noops for debug ports.
//Peter
next prev parent reply other threads:[~2006-12-07 9:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:08 Lu, Yinghai
2006-12-07 9:51 ` Peter Stuge [this message]
2006-12-11 14:53 ` [linux-usb-devel] [LinuxBIOS] " Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2006-12-09 3:16 [LinuxBIOS] [linux-usb-devel] " Lu, Yinghai
2006-12-09 10:54 ` Peter Stuge
2006-12-08 3:48 Lu, Yinghai
2006-12-08 7:14 ` Greg KH
2006-12-08 8:52 ` Yinghai Lu
2006-12-08 7:42 ` Eric W. Biederman
2006-12-08 8:53 ` Yinghai Lu
2006-12-08 9:07 ` Eric W. Biederman
2006-12-13 7:00 ` Yinghai Lu
2006-12-13 7:29 ` Eric W. Biederman
2006-12-13 10:09 ` Yinghai Lu
2006-12-13 10:41 ` Yinghai Lu
2006-12-07 22:06 Lu, Yinghai
2006-12-06 0:00 Lu, Yinghai
2006-12-05 23:29 Lu, Yinghai
2006-12-05 23:50 ` Eric W. Biederman
2006-12-06 15:31 ` Segher Boessenkool
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=20061207095116.27665.qmail@cdy.org \
--to=stuge-linuxbios@cdy.org \
--cc=ak@suse.de \
--cc=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxbios@linuxbios.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
all inboxes | Powered by JetHome®