On Tuesday 10 June 2003 21:04, David Brownell wrote:
> That is, it's a USB host. Yes > > Unidirectional is probably bad, you'd need some status exchange. I wondered about that, but I figured I'd start by hoping for the best possible case. > There's the DFU class spec, which resembles overkill but should > give you some ideas. Errors do happen, particularly since a > lot of those cables are not robustly designed, and you'd need > to detect and recover from them. (Like, by network checksums > and retransmissions!) :) Yes. From an implementation perspective, using the network sounds simpler and more flexible. But going without it reduces the amount of configuration our users have to do, and the amount of support that we have to do. > Many of the cables just pass bulk along with few problems > beyond whether they want some connection setup handshake. > So writing your own driver should be easy. We're still considering our options at this point, but now I at least have some idea of the work involved if we choose this route. Thanks for the help. Greg ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
