Subject: Re: kern/24636 (Re: kern/25041: USB isochronous transfers)
To: Matthew Orgass <email@example.com>
From: Iain Hibbert <firstname.lastname@example.org>
Date: 05/04/2006 17:26:34
On Thu, 4 May 2006, Matthew Orgass wrote:
> On 2006-05-03 email@example.com wrote:
> > 4. http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=24636
> > "potential invalid memory access"
> > Another one that could probably be closed? the changes mentioned
> > here have already been actioned and he mentions the issue of the done
> > method touching the xfer though not quite in this context.
> The first patch in this PR has not been applied yet (usbd_transfer uses
> xfer after the transfer even when not synchronous).
Oops yes, my mistake sorry .. I think that really, if somebody were to go
at this then it would be beneficial to rearrange the methodology such that
the callback was the last thing to be done and that it could not be called
before usbd_transfer returned.
I found it a bit strange to see that usbd_transfer can return
NORMAL_COMPLETION for asynchronous requests (for isoc anyway, I've not
seen it on a bulk pipe)