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 support for EMAC backhaul driver #85
Conversation
This requires ARMmbed/mbed-os#5944 |
c4c008b
to
0579173
Compare
9c1e22b
to
94a6915
Compare
Reworked to use default network interface API. Still not switched the default to EMAC. Guess we should? |
Note EMAC K64F driver still suffers from "cable disconnect start-up jam" so would be a functional regression from Nanostack version. |
Add new EMAC backhaul driver option that uses new mbed OS 5.9 EMAC and default network interface APIs. This should work for any Ethernet EMAC driver, and can work with appropriately-engineered Wifi drivers - see README.md for more details.
EMAC changes increase static allocation, meaning we don't quite fit in an IAR K64F build any more.
No longer builds with mbed OS 5.9 due to collision with EMAC driver. That EMAC driver is now usable, so no need for the Nanostack one anyway.
Change JSON files to select EMAC driver, rather than native Nanostack. This is currently a minor functional regression for K64F - the EMAC driver doesn't start gracefully if the cable isn't connected.
FYI, it looks like this commit is causing the currently generated 5.8.6 patch release to not build, due to the new config options.
Does this application still build in 5.8? |
@kjbracey-arm Changes for 5.9 should not land on master until 5.9 is released as this breaks 5.8 compatibility. Instead these changes should have gone on the OOB branch. Can you please do that and restore master to 5.8 compatibility. |
Add new EMAC backhaul driver option that uses new mbed OS 5.9 EMAC and default network interface APIs. This should work for any Ethernet EMAC driver, and can work with appropriately-engineered Wifi drivers - see README.md for more details.