> What I'm talking about is an ARC requirement to *disclose* non-DDI > interface consumption by drivers, and to strongly discourage the > practice of going outside of the DDI for device drivers. I think that > *is* an issue for PSARC at least.
How do you envision to enforce this in practice? Should C-team communicate back to PSARC? It used to be mostly one-way, making it bounce back and forth is thickening the process, while we're trying to thin it, to encourage external contributors. > (We're talking about interfaces here, not implementation.) In this particular case, the line is unclear. A minor bugfix can turn a DDI compliant driver into a non-compliant one. In my mind it's more implementation (think "lint clean") than architecture. -Artem
