On Fri, Dec 19, 2003 at 08:38:32PM +0100, David Mittelstädt wrote:
The nvidia module doesnt change anything. But am i right, if i asume, the UHCI driver is the cause of the error?
No, it looks like it's a driver error. The host driver is returning -EINVAL, which if you look in the Documentation/usb/error-codes.txt file shows: -EINVAL a) Invalid transfer type specified (or not supported) b) Invalid interrupt interval (0<=n<256)
Hmm, that's not quite right. Interval zero is illegal for interrupt or iso ... pass "1" for one frame (except at high speed). For ISO, intervals are log2 ... so "1" is period 2^(1-1) = 1, "3" is 2^(3-1) = 4, etc. and most HCDs won't support 2^(256-1)=? periods.
My guess would be that your ISO driver still thinks it's running on 2.4, where only one ISO period is supported.
- Dave
p.s. There are likely other reasons EINVAL is reported too.
c) more than one interrupt packet requested d) ISO: number_of_packets is < 0
So that points to the driver trying to submit an invalid urb.
Where would be the right place, to post this issue?
To the dvb driver authors :)
thanks,
greg k-h
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
