| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
An effor was made to increase modularity of device code. It was a
partial success. IP adress, communications port, and wifi login
details had to be made static and visible in main.
Time is scarce and I am not about to push this further.
Signed-off-by: Ramūnas Mažeikis <ramunasnezinomas@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
Parts of protocol specific for device are implementepd to reflect the
fact that the device is a client. This effectively means that device
gets a single connection only and severe memory restrictions about
which the daemon might get informed about in the future.
Signed-off-by: Ramūnas Mažeikis <ramunasnezinomas@gmail.com>
|
|
|
Most functions exposed in protocol.h take a connection descriptor
(cd_t) as first argument. This allows for multiple connections. Device
gets only one connection which means that cd_t is effectively 0 all
the time.
Additionaly, any function that actually does anything with a
connection descriptor instead of just passing it to another function
must be implemented separately in device and daemon.
Signed-off-by: Ramūnas Mažeikis <ramunasnezinomas@gmail.com>
|
Ramūnas Mažeikis
