Skip to content

Reduce K64F Ethernet driver to 1 thread #4996

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
Sep 5, 2017

Conversation

kjbracey
Copy link
Contributor

Save 1K of RAM by using only 1 thread for RX and TX, and running the PHY check in lwIP's context.

This makes the driver function more a bit more like the Nanostack one in https://github.com/ARMmbed/sal-nanostack-driver-k64f-eth, and could be viewed as a first step towards unification as an EMAC driver.

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 31, 2017

cc @mikaleppanen

Save 1K of RAM by using only 1 thread for RX and TX, and
running the PHY check in lwIP's context.
@mikaleppanen
Copy link

Looks good to me.

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 4, 2017

/morph test-nightly

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 4, 2017

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Sep 5, 2017

Result: SUCCESS

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

/morph test-nightly

Output

mbed Build Number: 1213

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.

5 participants