en:developers:documentation:nl80211
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:developers:documentation:nl80211 [2019/05/28 08:46] Johannes Berg [vendor-specific API] |
en:developers:documentation:nl80211 [2019/05/28 11:25] Johannes Berg [vendor-specific API] |
||
|---|---|---|---|
| Line 57: | Line 57: | ||
| - Example users/use cases of the API shall be documented. | - Example users/use cases of the API shall be documented. | ||
| - The newly proposed API shall be subject to stable API rules. | - The newly proposed API shall be subject to stable API rules. | ||
| - | - The content of the NL80211_ATTR_VENDOR_DATA shall be documented. | + | - Unless the data inside NL80211_ATTR_VENDOR_DATA is just an opaque blob not used by the driver (but e.g. by firmware), sub-attributes shall be used inside of it, and those shall be documented. |
| - Vendor command and sub-attribute definitions shall be in a common header file location (TBD, e.g. include/uapi/nl80211-vnd-*.h) | - Vendor command and sub-attribute definitions shall be in a common header file location (TBD, e.g. include/uapi/nl80211-vnd-*.h) | ||
| - Patches introducing such commands shall be submitted separately, not "buried" in big driver patchsets. Give them a "nl80211: vendor-cmd: " prefix to make them easily identifiable. | - Patches introducing such commands shall be submitted separately, not "buried" in big driver patchsets. Give them a "nl80211: vendor-cmd: " prefix to make them easily identifiable. | ||
en/developers/documentation/nl80211.txt · Last modified: 2024/02/27 19:24 by Johannes Berg
Page Tools
