Alan Stern wrote:
On Wed, 7 Jan 2004, Stavros Markou wrote:
Hi,
Thanks for your quick and accurate answer. It worked !!!
Are you gonna include this change to the upcoming 2.6.1 kernel ?
I am going to include it, along with other changes to
__usb_reset_device(), but I don't know if it wil
On Wed, 7 Jan 2004, Stavros Markou wrote:
> Hi,
>
> Thanks for your quick and accurate answer. It worked !!!
> Are you gonna include this change to the upcoming 2.6.1 kernel ?
I am going to include it, along with other changes to
__usb_reset_device(), but I don't know if it will be ready in time
Hi,
Thanks for your quick and accurate answer. It worked !!!
Are you gonna include this change to the upcoming 2.6.1 kernel ?
Stavros Markou.
Alan Stern wrote:
On Wed, 7 Jan 2004, Stavros Markou wrote:
Hi,
I wonder how can I find out the port number my device was plugged in
during probing
On Wed, 7 Jan 2004, Stavros Markou wrote:
> Hi,
>
> I wonder how can I find out the port number my device was plugged in
> during probing function of driver. I use a ported form kernel
> __usb_reset function and I see that there is a check for all
> parent->maxchild which in my case fails to f
Hi,
I wonder how can I find out the port number my device was plugged in
during probing function of driver. I use a ported form kernel
__usb_reset function and I see that there is a check for all
parent->maxchild which in my case fails to find a match between my usb
device and parent->children
