mirror of
https://github.com/meshtastic/firmware.git
synced 2025-12-22 10:42:49 +00:00
Update protos
This commit is contained in:
Submodule protobufs updated: a0fe9ec861...6b46e42a65
@@ -501,7 +501,7 @@ typedef PB_BYTES_ARRAY_T(256) MeshPacket_encrypted_t;
|
|||||||
typedef struct _MeshPacket {
|
typedef struct _MeshPacket {
|
||||||
/* The sending node number.
|
/* The sending node number.
|
||||||
Note: Our crypto implementation uses this field as well.
|
Note: Our crypto implementation uses this field as well.
|
||||||
See [crypto](/docs/developers/firmware/encryption) for details.
|
See [crypto](/docs/about/overview/encryption) for details.
|
||||||
FIXME - really should be fixed32 instead, this encoding only hurts the ble link though. */
|
FIXME - really should be fixed32 instead, this encoding only hurts the ble link though. */
|
||||||
uint32_t from;
|
uint32_t from;
|
||||||
/* The (immediatSee Priority description for more details.y should be fixed32 instead, this encoding only
|
/* The (immediatSee Priority description for more details.y should be fixed32 instead, this encoding only
|
||||||
@@ -529,7 +529,7 @@ typedef struct _MeshPacket {
|
|||||||
needs to be unique for a few minutes (long enough to last for the length of
|
needs to be unique for a few minutes (long enough to last for the length of
|
||||||
any ACK or the completion of a mesh broadcast flood).
|
any ACK or the completion of a mesh broadcast flood).
|
||||||
Note: Our crypto implementation uses this id as well.
|
Note: Our crypto implementation uses this id as well.
|
||||||
See [crypto](/docs/developers/firmware/encryption) for details.
|
See [crypto](/docs/about/overview/encryption) for details.
|
||||||
FIXME - really should be fixed32 instead, this encoding only
|
FIXME - really should be fixed32 instead, this encoding only
|
||||||
hurts the ble link though. */
|
hurts the ble link though. */
|
||||||
uint32_t id;
|
uint32_t id;
|
||||||
|
|||||||
Reference in New Issue
Block a user