All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang YanQing <udknight@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Anil Nair <anilcoll90@gmail.com>, Greg KH <greg@kroah.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org
Subject: Re: [RFC]Is usb port number fixed?
Date: Tue, 24 Apr 2012 23:58:43 +0800	[thread overview]
Message-ID: <20120424155843.GA3804@udknight> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1204241010270.1511-100000@iolanthe.rowland.org>

On Tue, Apr 24, 2012 at 10:14:05AM -0400, Alan Stern wrote:
> In drivers/usb/core/hub.c, look through the hub_events() routine.  
> There are several function calls similar to this one:
> 
> 			ret = hub_port_status(hub, i,
> 					&portstatus, &portchange);
> 
> Here i is the port number.  This asks the hub to send back status and 
> change information for port i.  (See also the code for the 
> hub_port_status() and get_port_status() routines.)

Thanks, I get it.

On Tue, Apr 24, 2012 at 07:52:44PM +0530, anil wrote:
> The USB specification Table 11-13 describes the hub descriptor in
> detail.
> The following data structure struct usb_hub_descriptor defined in
> "drivers/usb/core/hub.h" of Linux  Kernel source contains information
> about the hub descriptor,
> 
>                       struct usb_hub_descriptor {
>                             _u8 bDescLength;
>                           _u8 bDescriptorType;
>                              _u8 bNbrPorts;
>                        _le16 wHubCharacteristics;
>                           _u8 bPwrOn2PwrGood;
>                          _u8 bHubContrCurrent;
>                                    }
> 
> The bNbrPorts  member contains information on the number of
> downstream-facing ports the hub supports. The structure which i have
> provided is in reference to Linux Kernel Version 2.6 series for Linux
> Kernel Version 3.0+, Please consult an expert.
>   	Is this information you wanted?
> 

Yes, It is want I wanted.But maybe "11.5.3.1 Labeling" show more footprint.

Thanks, all guys.
All you give me a very good explanation about the sentence below:

"High quality support from experts available instantly over the Internet at
no charge has played a major role in stitching together a huge Linux community"

which come from the <<Essential Linux Device Drivers>>.

Cheers.

Udknight

  reply	other threads:[~2012-04-24 15:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHkwNT=DTjdhZmEg+SFGOVi+ZcS-NpHWH8Hh3XV+-BPzHRC7NA@mail.gmail.com>
2012-04-22 12:47 ` [RFC]Is usb port number fixed? Alan Stern
2012-04-23  1:52   ` Wang YanQing
2012-04-23 15:13     ` Alan Stern
2012-04-24  2:16       ` Wang YanQing
2012-04-24 14:14         ` Alan Stern
2012-04-24 15:58           ` Wang YanQing [this message]
2012-04-24 14:22         ` anil
2012-04-24  2:24       ` Wang YanQing
2012-04-20  9:25 Wang YanQing
2012-04-20  9:37 ` Wang YanQing
2012-04-20 15:37   ` Greg KH
     [not found]     ` <CAHkwNT=VW8qF-7QRxpiaWkmQm0UFdsbahFLhT-PCc4OMnVs1Gg@mail.gmail.com>
2012-04-20 16:19       ` Greg KH
2012-04-21  0:32     ` Alan Stern
2012-04-21  5:56       ` Wang YanQing
2012-04-21 17:23         ` Alan Stern

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=20120424155843.GA3804@udknight \
    --to=udknight@gmail.com \
    --cc=anilcoll90@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.