| commit | ca53d2bf80cc0155eb2c4d5f5fcbe1aa9d6edc9a | [log] [tgz] |
|---|---|---|
| author | Fabian Pflug <fabian.pflug@grandcentrix.net> | Tue Jul 23 07:39:27 2024 +0200 |
| committer | Anas Nashif <anas.nashif@intel.com> | Sat Jul 27 10:42:45 2024 +0300 |
| tree | 641f0bad89b8fd38b234edb341b341a91bfeb7e4 | |
| parent | 293fa118df91d7b4e6f7236c452e30399c15eee0 [diff] |
net: l2: ieee802154: mgmt: allow beacon payload The standard does allow for a optional beacon payload, which gets lost during scan, that could be interesting for the application to access in the NET_EVENT_IEEE802154_SCAN_RESULT callback. See section 7.3.1.6 in IEEE Std 802.15.4 for more information about the beacon payload field. And section 7.3.1 and figure 7-5 about general beacon frame format. Signed-off-by: Fabian Pflug <fabian.pflug@grandcentrix.net>