Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add IEEE 802.15.4 support #379

Draft
wants to merge 2 commits into
base: zephyr
Choose a base branch
from

Conversation

martinjaeger
Copy link
Member

Draft PR to show current status of porting to Zephyr.

Code compiles, but is not yet tested.

@sylvioalves There are some files which are not needed for Zephyr. How do you typically handle this? Should the entire component folder be copied so that it's easier to compare it to upstream ESP-IDF files or should we just use files required by Zephyr?

Commit hash in ESP-IDF: a2f420a36ecf8cd19b443adde1d75e5eaecc6309

Signed-off-by: Martin Jäger <[email protected]>
FreeRTOS-related code (e.g. locks) are replaced with Zephyr-specific
equivalents.

Signed-off-by: Martin Jäger <[email protected]>
@marekmatej
Copy link
Collaborator

marekmatej commented Dec 12, 2024

How do you typically handle this? Should the entire component folder be copied so that it's easier to compare it to upstream ESP-IDF files or should we just use files required by Zephyr?

@martinjaeger This is usually done by this repo https://github.com/espressif/esp-hal-3rdparty by fetching only chosen components. The rest of the work (like you did here) is done in the hal_espressif.

@marekmatej
Copy link
Collaborator

@martinjaeger We are using these adaptation layers for BT and WiFi (zephyr/esp32c6/src/wifi/esp_wifi_adapter.c, zephyr/esp32c3/src/bt/esp_bt_adapter.c). Have you considered creating one for 802154?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants