On Wed, 4 Jul 2007, jidong xiao wrote:
> Still consider following piece of code, I see there is a change in
> this part of code,here showed the same part of code but came from
> different kernel version,one is sampled from kernel 2.6.10,while
> another is sampled from kernel 2.6.21.
>
> inside hu
Still consider following piece of code, I see there is a change in
this part of code,here showed the same part of code but came from
different kernel version,one is sampled from kernel 2.6.10,while
another is sampled from kernel 2.6.21.
inside hub_events() sampled from drivers/usb/core/hub.c, 2.6.
On 7/3/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 3 Jul 2007, Felipe Balbi wrote:
>
> > Hi Allan,
> >
> > let me get this same thread to ask you the following
>
> > How could I force my usb host controller to re-enumerate everything
> > attached on the bus through userspace?? would it be s
On Tue, 3 Jul 2007, Felipe Balbi wrote:
> Hi Allan,
>
> let me get this same thread to ask you the following
> How could I force my usb host controller to re-enumerate everything
> attached on the bus through userspace?? would it be some sort of
> control message???
The easiest way is to unbind
Hi Allan,
let me get this same thread to ask you the following
On 7/3/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 3 Jul 2007, jidong xiao wrote:
>
> > What's the difference between event_bits and change_bits?
> > I just cannot understand why we need two variables.
> >
> >
> > 188 stru
On Tue, 3 Jul 2007, jidong xiao wrote:
> What's the difference between event_bits and change_bits?
> I just cannot understand why we need two variables.
>
>
> 188 struct usb_hub {
> ...
> 205 unsigned long event_bits[1]; /* status
> change bitmask */
> 206
What's the difference between event_bits and change_bits?
I just cannot understand why we need two variables.
188 struct usb_hub {
...
205 unsigned long event_bits[1]; /* status
change bitmask */
206 unsigned long change_bits[1]; /* ports with
