3 ms·
It frustrates me that it just goes "Interrupt fires". There's a whole lot that goes on between the USB bus receiving the packet and HID driver - I mean, even m
by TheLoneWolfling 12y ago
It frustrates me that it just goes "Interrupt fires".
There's a whole lot that goes on between the USB bus receiving the packet and HID driver - I mean, even making the processor branch is non-trivial.
- 300bps 12y agoOn the network level, seems to have missed the ARP protocol entirely. Didn't seem to mention the function of the multiple routers between client and server, the calculations of netblock and subnet mask, role of firewalls between client and host, etc, etc. Probably missing off the top of my head at least 100 steps. If you sat down to write a paper on it he's probably missing closer to 1,000 discrete units of work in the overall process.
- aptwebapps 12y agoIt's a WIP. Scroll down and you'll see a lot more similar headings. The ellipsis is to indicate that the section is incomplete. Perhaps you can contribute?
- TheLoneWolfling 12y agoI don't know the details of that section myself - I'd love to find out, hence my disappointment that it wasn't there.
- jdbernard 12y agoI agree. Fork it, flesh out those details and submit a pull request. I get the feeling this is very much a work in progresses.
- TheLoneWolfling 12y agoI don't know the details of that section myself - I'd love to find out, hence my disappointment that it wasn't there.
- rasz_pl 12y ago>USB bus receiving the packet its not really receiving packets, its receiving data _you specifically requested in YOUR packet_. in USB only host is capable of generating traffic on the bus, your device cant generate any packets, only answer to them.
- TheLoneWolfling 12y agoAnd this is exactly the sort of thing that I wish it included, so I could learn about it. It's complex, I know it's complex, and I want to know what actually happens at that awkward fuzzy boundary between hardware and software.