diff options
| author | Jeremy Kerr <jk@ozlabs.org> | 2013-03-11 13:43:48 +0800 |
|---|---|---|
| committer | Jeremy Kerr <jk@ozlabs.org> | 2013-04-16 11:41:46 +0800 |
| commit | bd06734362bb727b09b943688d9b69aa0a84590d (patch) | |
| tree | 476072cae1d0d28b286928c5fba589bde4a2d9aa /ui/test/discover-test.c | |
| parent | b838cf777ed3d21b166f8daddd4b11fc75e07307 (diff) | |
| download | talos-petitboot-bd06734362bb727b09b943688d9b69aa0a84590d.tar.gz talos-petitboot-bd06734362bb727b09b943688d9b69aa0a84590d.zip | |
protocol: Separate device add from boot-option add messages
We want to cater for situations where boot options may be discovered
some time after we get notificiation about devices. For instance,
discovering boot options from DHCP configuration parameters. In this
case, we'll need to notify UIs of boot options appear some time after
the device (and/or other boot options on the same device) has appeared.
This change adds a new protocol message type,
PB_PROTOCOL_ACTION_BOOT_OPTION_ADD. We also rename
PB_PROTOCOL_ACTION_ADD to make it clear that it is just for devices.
The discover server is updated to send boot option add events at device
discover time, but we are now able to decouple this later.
We also update the clients to handle the boot option add events
separately.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Diffstat (limited to 'ui/test/discover-test.c')
0 files changed, 0 insertions, 0 deletions
