Linked by Thom Holwerda on Tue 21st Feb 2012 13:50 UTC, submitted by Ducky Johnson
Thread beginning with comment 508040
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
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.




Member since:
2012-02-19
As someone else mentioned above, this is no small feat.
Writing a USB stack is *really* hard. I helped a colleague who was working on a client (not host!) USB stack for the MSP430. Even with sample code and some support from TI, it took him almost a month to implement a subset of the ACM functions that we needed. I don't even want to think about what writing the USB host stack involves.