Linked by Thom Holwerda on Tue 21st Feb 2012 13:50 UTC, submitted by Ducky Johnson
Permalink for comment 508069
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2010-02-18
I think host support is easier.
Since in USB all communication is initiated by the host, the driver author gets to decide what to do and when.
For clients, you'll have to cope with whatever the host throws at you. (but to be fair: some devices are rather weird in what they answer)
But I only wrote a bunch of host drivers (ohci, uhci, ehci, some xhci stub, various class drivers) so far, and no client drivers.