Skip to content

Add support for ethernet-only configuration with Nanostack. #3547

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

Merged
merged 1 commit into from
Jan 12, 2017
Merged

Add support for ethernet-only configuration with Nanostack. #3547

merged 1 commit into from
Jan 12, 2017

Conversation

SeppoTakalo
Copy link
Contributor

This saves about 100kB of flash when using ethernet only configuration.
Otherwise only border router configuration was supporting ethernet.

Tested manually with mbed-os-cliapp.

Status

READY

Migrations

No

Deploy notes

If application wants to use Nanostack with ethernet only mode it can use following configuration

"target.features_add": ["NANOSTACK", "ETHERNET_HOST", "COMMON_PAL"],

@sg- @0xc0170 Please merge in.
This is needs to go in into patch releases of mbed OS 5.3, before we supply new nanostack binaries for 5.4 with API change.

This saves about 100kB of flash when using ethernet only configuration.
Otherwise only border router configuration was supporting ethernet.
@sg- sg- added the needs: CI label Jan 9, 2017
@0xc0170
Copy link
Contributor

0xc0170 commented Jan 11, 2017

Seems that continuous-integration/jenkins/pr-head did not report the result. I restarted it just now

@bridadan
Copy link
Contributor

/morph test-nightly

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 1383

All builds and test passed!

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.

6 participants