You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RFCs/0002-pluggable-discovery.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The pluggable discovery aims to provide a solution to these problems.
34
34
35
35
- Each port may provide metadata to identify a specific instance of the board (**serial number / MAC address**)
36
36
37
-
- Each port must have an **unique address**
37
+
- Each port must have an **unique address and protocol pair**
38
38
39
39
- A single device may expose multiple ports
40
40
@@ -195,14 +195,15 @@ The `remove` event looks like the following:
195
195
{
196
196
"eventType": "remove",
197
197
"port": {
198
-
"address": "/dev/ttyACM0"
198
+
"address": "/dev/ttyACM0",
199
+
"protocol": "serial"
199
200
}
200
201
}
201
202
```
202
203
203
-
the content is straightforward, in this case only the `address`field is reported.
204
+
the content is straightforward, in this case only the `address`and `protocol` fields are reported.
204
205
205
-
If the information about a port needs to be updated the discovery may send a new `add` message for the same port address without sending a `remove` first: this means that all the previous information about the port must be discarded and replaced with the new one.
206
+
If the information about a port needs to be updated the discovery may send a new `add` message for the same port address and protocol without sending a `remove` first: this means that all the previous information about the port must be discarded and replaced with the new one.
0 commit comments