sdcard_spi is the only driver in auto_init_storage and was previously
pulled in by fatsfs (because it's used on SD cards)
It does however make much more sense if the SD card driver pulls that in
so other file systems can be used on SD card too.
Instead of making a NETTYPE definition dependent on an implementation
module, this change makes it dependent on a pseudo-module for each
specific NETTYPE and makes the respective implementation modules
dependent on it.
This has two advantages:
- one does not need include the whole implementation module to
subscribe to a NETTYPE for testing or to provide an alternative
implementation
- A lot of circular dependencies related to GNRC could be untangled.
E.g. the only reason `gnrc_icmpv6` needs the `gnrc_ipv6` is because it
uses `GNRC_NETTYPE_IPV6` to search for the IPv6 header in an ICMPv6
when demultiplexing an ICMPv6 header.
This change does not resolve these dependencies or include usages where
needed. The only dependency change is the addition of the
pseudo-modules to the implementation modules.
The parameters of the MTD device (`sector_count`, `page_size`)
are only known after the device has been initialized.
Init the device before using it to avoid reading all 0 on e.g. SD cards.
The parameters of the MTD device (`sector_count`, `page_size`)
are only known after the device has been initialized.
Init the device before using it to avoid reading all 0 on e.g. SD cards.
The parameters of the MTD device (`sector_count`, `page_size`)
are only known after the device has been initialized.
Init the device before using it to avoid reading all 0 on e.g. SD cards.
Previously, TimerInit() explicitly set some values of the xtimer truct
to "0". This commit changes it to use a static struct initializer
`(xtimer_t){0}`. The advantage is that now this is independent of the
actual xtimer structure.
Now this also resets the remaining xtimer fields, but they're properly
re-populated elsewhere (by using xtimer_set_msg()).
With #10970 only existing *.c files will be added to SRC when using
the SUBMODULES mechanism, so SUBMODULES_NOFORCE (used to filter out
non existing source files) is now redundant so remove the usage.
Proto files can include other proto files.
E.g. nanopb comes with a `nanopb.proto` include that contains some
nanopb-specific extensions.
This patch makes it possible to include this file as well as specifying
additional proto include folders.
I added the include to `simple.proto` so it gets exercised by the test.
With the 3.0.0 update of monocypher the API changed enough to break
libcose compatibility. This PR removes monocypher from the crypto
options. It can be restored as soon as upstream libcose is updated to
restore compatibility
