This solves highly theoretical race conditions of file systems being
unmounted in an application while a shell `df` runs, fixes the previous
weird behavior that `/mountpoint/non-existant-path` could be df'd and
would even report that non-existant path as a file name, but more
practically ensures that an example of vfs_iter_mount_dirs is around.
... adding precision to the documentation where a corner case was
discovered during testing and is permitted.
The test is too large for one small board, just like the other existing
VFS test.
No current file system implements it, there is no defined semantic
difference between running fstatfs and the fallback currently
implemented, and there is practically no optimization gained from not
just running it through a single statvfs.
Add a basic SenML module and submodules with support for:
- Encoding SenML values as CBOR using NanoCBOR.
- Converting from Phydat to SenML.
- Reading and encoding SAUL sensors.
This makes FAT behave more like the other file systems supported by VFS.
The `fatfs_mtd_devs` array is populated internally so the application does
not have to handle this.
Implement a new module stdio_nimble, which uses nimble
for stdio. The characteristic for stdin is writable and
the characteristic for stdout uses the indicate mechanism
to publish the system's output to a connected device.
Data will be sent out asynchronously via callout functions.
The module can be enabled with "USEMODULE += stdio_nimble"
Co-authored-by: Francisco Molina <femolina@uc.cl>
The braces (which appear to do nothing) were keeping Doxygen from
grouping the three "Endpoint ID defition" parameters (apparently
intended to be grouped from the braces in the file) from being shown
together.
Moreover, they kept CONFIG_CORD_EXTRAARGS from showing.
... anchored both under "compile time configuration" and "Networking /
CoRE RD"
This makes the related configuration items visible on the same page.
Co-authored-by: Martine Lenders <mail@martine-lenders.eu>
The title is long enough that it is easily misread as "Client
Configuration" and skipped when looking for common configuration.
(Plus none of the other submodules of net_cord spell out the full "Core
RD Endpoint and Lookup Client" module name again,a dn all say "CoRE RD
Something".)
The RSSI values reported by LoRa transceiver can be less than -127.
Therefore, `int8_t` is not enough. This commit defines the RSSI of
`netdev_lora_rx_info` as `int16_t` and adapt the drivers accordingly
(sx126x, sx127x).
