Garrett D'Amore wrote:
> Artem Kachitchkine wrote:
>>
>> Why is this an ARC issue? Drivers don't usually go through ARC. it
>> should probably be on the ON C-Team Driver Checklist. Add DDICT to
>> the ON tool set and integrate it with wx.
>
> 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. (We're talking about interfaces
> here, not implementation.)
Sorry, I was suggesting methods for the general case. Yea, this is
pretty much a "PSARC only" issue.
Right now, drivers often don't need ARC involvement (beyond the
"register the name" paperwork - closed approved automatic). I think the
"closed approved" path is only appropriate (already) for DDI-compliant
drivers...
if <DDI-compliant>
-> closed approved automatic
else
-> fast-track (or greater)
I think the only thing we need to do is to advertise and enforce the
above, existing rule. The question is "how to enforce". I really don't
have a suggestion for that. (I suspect somebody will!)
- jek3
