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 | ||
|
en:developers:documentation:nl80211 [2019/05/28 11:16] Johannes Berg [vendor-specific API] |
en:developers:documentation:nl80211 [2024/02/27 19:24] (current) Johannes Berg add wifi prefix to subject |
||
|---|---|---|---|
| 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. | ||
| - | - Sub-attributes of the NL80211_ATTR_VENDOR_DATA shall usually be used (at least for driver code) and 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 "wifi: nl80211: vendor-cmd: " prefix to make them easily identifiable. |
| The goal with these rules is to enable use of vendor commands in a fashion that is transparent enough to allow later reuse by other components with similar needs, and then potentially defining "real" nl80211 API for the use case in question. | The goal with these rules is to enable use of vendor commands in a fashion that is transparent enough to allow later reuse by other components with similar needs, and then potentially defining "real" nl80211 API for the use case in question. | ||
| - | Patches will be merged through Kalle Valo's tree, but should also be reviewed by Johannes (cfg80211 maintainer). | ||
en/developers/documentation/nl80211.1559042186.txt.gz · Last modified: 2019/05/28 11:16 by Johannes Berg
Page Tools
