HI alan,
I am reading the descriptor and speed of the USB storage device, for
that I wrote an ioctl locally,
Here is the code segment returning error ---
ret = usb_control_msg(pRootHub, usb_rcvctrlpipe(pRootHub, 0),
USB_REQ_GET_STATUS, USB_DIR_IN | USB_RT_PORT, 0,
port_num + 1, portsts, sizeof(struct usb_hub_status),
5000/* HZ */);
if (ret < 0) {
err("3 HUB_PORT: --> %s (%d) failed (err = %d)",
__FUNCTION__, pRootHub->devnum, ret);
}
I am getting the above error:
Getting in depth, I am having two HCDs, How can I check which HCD is
being used ?
As this IOCTL is working prefect for the rear port which is using the
controller 0, with only one port.
While its giving the above error for front port, which is another
controller 1 with one port.
So I wanted to check whether controller is selected properly ...
Where I can check for it.
Many thanks
Prabhu
On Fri, Jun 19, 2009 at 10:01 PM, Alan Stern<stern@xxxxxxxxxxxxxxxxxxx> wrote:
> On Fri, 19 Jun 2009, Prabhu Chawandi wrote:
>
>> I am using the 2.6.18. What is the reason for that, reading the small
>> notes I could not makee out. :(
>>
>> On Fri, Jun 19, 2009 at 7:54 PM, Alan Stern<stern@xxxxxxxxxxxxxxxxxxx> wrote:
>> > On Fri, 19 Jun 2009, Prabhu Chawandi wrote:
>> >
>> >> Hi All,
>> >>
>> >> May I know, in what case the below error is thrown ...
>> >>
>> >> drivers/usb/core/devio.c: HUB_PORT: --> proc_usb_test (1) failed (err = -32)
>> >> drivers/usb/core/devio.c: HUB_PORT: --> proc_usb_test (1) failed (err = -32)
>> >
>> > It doesn't occur at all in recent versions of the kernel. What version
>> > did you see it in? What program were you running at the time?
>
> That message does not appear in the 2.6.18 kernel. It must have been
> printed by a program instead.
>
> What were you doing when this error message appeared?
>
> What program were you running?
>
> Alan Stern
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
