such fixes mean
API changes, but IMO not in the 2.4 series (until a
backport).
- Dave
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 07, 2002 8:58 AM
Subject: Re: [linux-usb-devel] Using interrupt URBs
> Hi,
>
> >>
Hi,
>> OK, thanks for that info. Following on from it - which fields
>> can I/need I set up again in the completion routine ?
>
> None of them. After you submit any URB, they're all
> read-only from the perspective of the driver. Yes, that
> is part of what makes the automagic resubmit model
>
David Brownell wrote:
>
> > I just wish ohci/uhci/??? all did the same thing when it comes to
> > interrupt URB's. (both in and out).
>
> There's also an issue of doing something close to right ... :)
>
Yea, I know..
this is the device I have:
P: Vendor=1292 ProdID=0258 Rev= 1.00
C:* #Ifs=
> > If you set the interval to anything other than 0, then it will
> > automatically resubmit for you. This is how interrupt URB's are
> > typically used.
>
> OK, thanks for that info. Following on from it - which fields
> can I/need I set up again in the completion routine ?
None of them. Afte
> > bulk is the same as "one-shot interrupt" with the only exception being
> > interrupt is earlier in the frame than bulk, so interrupt is
> > "guaranteed" to happen while bulk is not (on a heavily loaded bus).
Well, sort of. There's also a restriction that interrupt transfers
involve only one
Dan Streetman wrote:
>
> On Wed, 1 May 2002, Thomas Davis wrote:
>
> >Johannes Erdfelt wrote:
> >>
> >> On Wed, May 01, 2002, David Brownell <[EMAIL PROTECTED]> wrote:
> >> >
> >> > However, that's a UHCI-specific feature. Avoid it for
> >> > drivers that you expect to work on other HCs.
> >>
>
Hi,
> Depends on if you set the interval or not. An interval of 0 is what is
> called one shot and it'll be finished when the transfer has completed.
>
> If you set the interval to anything other than 0, then it will
> automatically resubmit for you. This is how interrupt URB's are
> typically u
On Wed, 1 May 2002, Thomas Davis wrote:
>Johannes Erdfelt wrote:
>>
>> On Wed, May 01, 2002, David Brownell <[EMAIL PROTECTED]> wrote:
>> >
>> > However, that's a UHCI-specific feature. Avoid it for
>> > drivers that you expect to work on other HCs.
>>
>> OHCI and EHCI are buggy then I guess. T
Johannes Erdfelt wrote:
>
> On Wed, May 01, 2002, David Brownell <[EMAIL PROTECTED]> wrote:
> >
> > However, that's a UHCI-specific feature. Avoid it for
> > drivers that you expect to work on other HCs.
>
> OHCI and EHCI are buggy then I guess. This is a feature that is actually
> useful and s
> > I have a question about the handling of interrupt URBs: once
> > an interrupt URB has been submitted (usb_submit_urb()), does it have
> > to be resubmitted by the completion routine, or does the USB system
> > automatically re-queue the URB once the completion routine returns ?
> > In the latt
On Wed, May 01, 2002, David Brownell <[EMAIL PROTECTED]> wrote:
> > > I have a question about the handling of interrupt URBs: once
> > > an interrupt URB has been submitted (usb_submit_urb()), does it have
> > > to be resubmitted by the completion routine, or does the USB system
> > > automaticall
On Wed, May 01, 2002, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have a question about the handling of interrupt URBs: once
> an interrupt URB has been submitted (usb_submit_urb()), does it have
> to be resubmitted by the completion routine, or does the USB system
> automatically re-qu
12 matches
Mail list logo
