4 ms·
The USB spec is like, what, 500 pages? That is impressive.
by amelius 2y ago
The USB spec is like, what, 500 pages?
That is impressive.
- tedunangst 2y agoI couldn't even transcribe 500 pages in three hours.
- bartvk 2y agoYou don't need to read the nitty-gritty of the USB spec itself, having a general idea of its capabilities is enough. The kernel gives you a bunch of functions to work with. You can learn it by simply reading the code of the most simple driver that you can find in the kernel source. Then you can step up, and find a more difficult one.
- codedokode 2y agoIt would be better if you could just read doxygen docs or something like this instead of having to reverse-engineer someone's else code. Because the code is just an example of using functions and doesn't give their complete description. If you write something like Linux kernel, write doc comments.
- userbinator 2y agoAlso, much of the USB spec deals with the hardware level and device side implementation.
- pantalaimon 2y agoA good driver API will hide that all and make sure an individual USB driver does not have to care about the USB spec - that’s the job of the shared USB core code.
- seba_dos1 2y ago...and also mostly irrelevant here.