Home
last modified time | relevance | path

Searched refs:identity (Results 1 – 25 of 43) sorted by relevance

12

/Zephyr-Core-2.7.6/samples/modules/canopennode/objdict/
DCO_OD.c106 { (void *)&CO_OD_ROM.identity.maxSubIndex, 0x05, 0x1 },
107 { (void *)&CO_OD_ROM.identity.vendorID, 0x85, 0x4 },
108 { (void *)&CO_OD_ROM.identity.productCode, 0x85, 0x4 },
109 { (void *)&CO_OD_ROM.identity.revisionNumber, 0x85, 0x4 },
110 { (void *)&CO_OD_ROM.identity.serialNumber, 0x85, 0x4 },
DCO_OD.h499 /*1018 */ OD_identity_t identity; member
613 #define OD_identity CO_OD_ROM.identity
/Zephyr-Core-2.7.6/samples/bluetooth/peripheral_sc_only/src/
Dmain.c55 const bt_addr_le_t *identity) in identity_resolved() argument
60 bt_addr_le_to_str(identity, addr_identity, sizeof(addr_identity)); in identity_resolved()
/Zephyr-Core-2.7.6/doc/guides/arch/
Dx86.rst17 memory are identity mapped and thus giving the appearance of execution
37 (:file:`arch/x86/gen_mmu.py`) identity maps the physical addresses
40 the entries for identity mapping at the page directory level are
42 the identity mapping of physical memory. This unmapping must be done
44 restricted memory via physical addresses. Since the identity mapping
/Zephyr-Core-2.7.6/doc/reference/networking/
Dlldp.rst14 protocol used by network devices for advertising their identity, capabilities,
Dlwm2m.rst371 initialization we need to create a PSK and identity. These need to match
388 resource. Lastly, set the client identity and PSK resources.
396 /* Set the client identity */
/Zephyr-Core-2.7.6/samples/bluetooth/peripheral_identity/
DREADME.rst9 This sample demonstrates use of multiple identity and the ability to be
/Zephyr-Core-2.7.6/subsys/bluetooth/mesh/
Dsubnet.h63 uint8_t identity[16]; /* IdentityKey */ member
Dcfg_cli.c802 uint8_t *identity; member
810 uint16_t net_idx, identity; in node_identity_status() local
824 identity = net_buf_simple_pull_u8(buf); in node_identity_status()
830 if (param && param->identity) { in node_identity_status()
831 *param->identity = identity; in node_identity_status()
2448 uint8_t *status, uint8_t *identity) in bt_mesh_cfg_node_identity_set() argument
2460 .identity = identity, in bt_mesh_cfg_node_identity_set()
2490 uint8_t *identity) in bt_mesh_cfg_node_identity_get() argument
2502 .identity = identity, in bt_mesh_cfg_node_identity_get()
Dsubnet.c313 err = bt_mesh_identity_key(key, keys->identity); in net_keys_create()
319 BT_DBG("IdentityKey %s", bt_hex(keys->identity, 16)); in net_keys_create()
Dgatt_services.c469 err = bt_encrypt_be(sub->keys[SUBNET_KEY_TX_IDX(sub)].identity, tmp, in node_id_adv()
/Zephyr-Core-2.7.6/doc/development_process/
Dmodifying_contributions.rst60 the original sign-off line and author identity, or
62 *own* sign-off line and author identity). In this case, the developer
/Zephyr-Core-2.7.6/
DCODE_OF_CONDUCT.md8 size, disability, ethnicity, sex characteristics, gender identity and expression,
10 appearance, race, religion, or sexual identity and orientation.
/Zephyr-Core-2.7.6/doc/reference/bluetooth/
Dhci.txt558 The Identity_Root parameter may be all zeros to indicate no identity root key
559 being available for a given static address. The identity root key returned from
563 it is recommended to return an identity root key (if available) from this
565 the Read_Key_Hierarchy_Roots command to return the identity root key (if only
598 | | missing identity root key. |
619 This command shall return the identity root key and encryption root key
624 The identity root key and encryption root key may be used for the controllers
627 command that have its dedicated identity root key assigned.
630 identity root key, the returned Identity_Root value may be used. It is however
/Zephyr-Core-2.7.6/include/bluetooth/mesh/
Dcfg_cli.h1030 uint8_t *status, uint8_t *identity);
1046 uint8_t *identity);
/Zephyr-Core-2.7.6/include/arch/x86/
Dmemory.ld39 * the same as its physical location, although an identity mapping for RAM
/Zephyr-Core-2.7.6/subsys/bluetooth/host/
DKconfig502 bool "Perform active scanning using local identity address"
506 identity address as the scanner address. By default the stack will
508 disclosing local identity information. By not scanning with the
509 identity address the scanner will receive directed advertise reports
510 for for the local identity. If this use case is required, then enable
549 Maximum number of supported local identity addresses. For most
/Zephyr-Core-2.7.6/tests/bluetooth/tester/src/
Dmesh.c2033 uint8_t identity; in config_node_identity_set() local
2041 &status, &identity); in config_node_identity_set()
2050 net_buf_simple_add_u8(buf, identity); in config_node_identity_set()
2064 uint8_t identity; in config_node_identity_get() local
2072 &identity); in config_node_identity_get()
2081 net_buf_simple_add_u8(buf, identity); in config_node_identity_get()
Dgap.c131 const bt_addr_le_t *identity) in le_identity_resolved() argument
138 ev.identity_address_type = identity->type; in le_identity_resolved()
139 memcpy(ev.identity_address, identity->a.val, in le_identity_resolved()
/Zephyr-Core-2.7.6/include/bluetooth/
Dconn.h868 const bt_addr_le_t *identity);
/Zephyr-Core-2.7.6/doc/reference/kernel/scheduling/
Dindex.rst16 opportunity to change the identity of the current thread. These points
29 Whenever the scheduler changes the identity of the current thread,
/Zephyr-Core-2.7.6/doc/security/
Dsensor-threat.rst258 (mapping them to a device identity), having these certificates
271 sent until the device has verified the identity of the server.
328 iii. Removing the device identity and certificate from the
/Zephyr-Core-2.7.6/arch/
DKconfig620 address from DTS, in which case RAM will be identity-mapped. Some
627 Otherwise, if RAM isn't identity-mapped:
633 regions if RAM is not identity-mapped, or the virtual and physical
/Zephyr-Core-2.7.6/boards/arm/cc3235sf_launchxl/doc/
Dindex.rst266 Once the connection succeeds, the network co-processor keeps the AP identity in
/Zephyr-Core-2.7.6/boards/arm/cc3220sf_launchxl/doc/
Dindex.rst266 Once the connection succeeds, the network co-processor keeps the AP identity in

12