An even bigger issue is that small customers tend to use a different feature set than large-volume (or very-large-volume) customers. If you're building a high-e

An even bigger issue is that small customers tend to use a different feature set than large-volume (or very-large-volume) customers. If you're building a high-end or enterprise access point, the functionality you care about is probably the least tested and least-well-maintained part of the massive driver codebase - to the extent that the thing won't even compile with the proper #defines. So the documentation isn't just important for understanding the chip, it's also necessary for rewriting the driver. .... and that's what I spent cumulatively about a year of my life on. Ugh.