Timeout

QNX Newsgroups (Archives) qdn.public.ddk.usb
1

I handle a device that will disable USB fonctionnality all together
when performing certain command.

For example I can ask the device to perform a memory test, which
will render the device totaly unresponsive for 3 seconds.

Although I specified to usbd_io USBD_TIME_INFINITY it will
timeout in about 1 sec or so. Problem I’m expecting a result back
from the command which is lost because of the timeout.

Is this a timeout I can control or is it native to the USB protocol ?

  • Mario
2

Is this question too stupid to deserve an answer?
If the answer is in the USB spec just tell me and I’ll
go through it again…

“Mario Charest” <mcharest@nozinformatic.com> wrote in message
news:3aed7a3b.4819460@inn.qnx.com…

I handle a device that will disable USB fonctionnality all together
when performing certain command.

For example I can ask the device to perform a memory test, which
will render the device totaly unresponsive for 3 seconds.

Although I specified to usbd_io USBD_TIME_INFINITY it will
timeout in about 1 sec or so. Problem I’m expecting a result back
from the command which is lost because of the timeout.

Is this a timeout I can control or is it native to the USB protocol ?

  • Mario
3

Mario Charest <mcharest@nozinformatic.com> wrote:


I handle a device that will disable USB fonctionnality all together
when performing certain command.

For example I can ask the device to perform a memory test, which
will render the device totaly unresponsive for 3 seconds.

Although I specified to usbd_io USBD_TIME_INFINITY it will
timeout in about 1 sec or so. Problem I’m expecting a result back
from the command which is lost because of the timeout.

The stacks currently have a 2 second timeout on control transfers. The
next DDK will honour the usbd_io timeout on control transfers.

4

On 3 May 2001 11:54:39 GMT, Kevin Chiles <kchiles@qnx.com> wrote:

Mario Charest <> mcharest@nozinformatic.com> > wrote:


I handle a device that will disable USB fonctionnality all together
when performing certain command.

For example I can ask the device to perform a memory test, which
will render the device totaly unresponsive for 3 seconds.

Although I specified to usbd_io USBD_TIME_INFINITY it will
timeout in about 1 sec or so. Problem I’m expecting a result back
from the command which is lost because of the timeout.

The stacks currently have a 2 second timeout on control transfers. The
next DDK will honour the usbd_io timeout on control transfers.

Thanks