Skip to content

Iee802154 mac#1

Closed
moritzholzer wants to merge 10000 commits intomasterfrom
iee802154_mac
Closed

Iee802154 mac#1
moritzholzer wants to merge 10000 commits intomasterfrom
iee802154_mac

Conversation

@moritzholzer
Copy link
Owner

Contribution description

Testing procedure

Issues/PRs references

benpicco and others added 30 commits December 8, 2025 13:21
…rt-agnostic-api

sys/net/*coap: Make APIs (more) transport agnostic
…icit-build

build-system: fix RIOTBOOT_SKIP_COMPILE
This can be used to get the highest value out of a list of numeric
numbers in a Makefile variable separated by whitespace.
This adds a mechanism for modules to declare requirements on the thread
stack size in their `Makefile.dep` and let the build system then
override the default stack size, if any requirements are declared.

The motivation is to allow multiple modules to have special requirements
without causing conflicts, as just adding the following to their
`Makefile.include` would do:

```Makefile
CFLAGS += -DEVENT_THREAD_MEDIUM_STACKSIZE=<MAGIC_NUMBER>
```

Instead, the new mechanism would work by having them both declare in
their `Makefile.dep`:

```Makefile
EVENT_THREAD_MEDIUM_STACKSIZE_MIN +=
```

The build system then picks the maximum number in
`EVENT_THREAD_MEDIUM_STACKSIZE_MIN` and exposes this as stack size, if
any module did declare a minimum requirement.

Co-authored-by: benpicco <benpicco@googlemail.com>
This adds a simple integration test for declaring the stack size
requirements in modules.
The netapi notify API enables protocol-independent, cross-layer
notification events.
Lower layers in the network stack can use this to inform upper
layers of network events.
If a new L2 connection was established, the node should be inserted in
the neighbor cache.
For 6LN nodes, NIB will never start the usual neighbor discovery process
because it can directly resolve the link-layer address from the IPv6
address. Thus we have to manually add such nodes to the NC by building
the IPv6 address from the L2 address.

If a L2 connection closed, the node is removed again from the NC.
Iterate through all parents whose address match `addr`.
In most cases there will only be a single parent, but if
`GNRC_RPL_INSTANCES_NUMOF > 1` then one node can be parent in multiple
DODAGs.
Handle netapi notification for discovered and unreachable neighbors.
For newly discovered neighbors, send a DIS message to the node. For
unreachable nodes trigger a timeout for RPL parents that match the
address.
`gnrc_rpl` now receives a notification if a new node is reachable (i.e.,
connected) and sends a DIS. No need anymore to also do it in rpble.
…json-as-binary

.gitattributes: mark package-lock.json as binary
…-again

doc/starlight: remove copy folder hacks
…ize-build-system-integration

sys/event: manage event thread size via build system
gnrc, nimble/ble: notify network layer of BLE connection events
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.