On Tue, 1 Aug 2006, Jared Holzman wrote: > Thanks, > > I manage to figure out the ability to blacklist after I'd already posted > my query to the list. The driver now successfully claims the interfaces. > This does not seem the most ideal way to do it unless you can blacklist > a module per device, otherwise using this driver would mean no other > snd_usb_audio based devices would be able to work.
Yes, it's a definite disadvantage of that approach. > I was unaware that > you could release an interface from another module, but I'll give it a > whirl. > > Another quick question, what does the status -EOVERFLOW mean for > individual isochronous packets? All the normal USB error codes are explained in Documentation/usb/error-codes.txt. -EOVERFLOW status means the received data packet was larger than expected. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
