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

Feature Request: Make wizphy_setphypmode accessable #2082

Open
traxanos opened this issue Apr 1, 2024 · 3 comments
Open

Feature Request: Make wizphy_setphypmode accessable #2082

traxanos opened this issue Apr 1, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@traxanos
Copy link
Contributor

traxanos commented Apr 1, 2024

Hello,

is it possible to make wizphy_setphypmode() accessible? I would like to switch from EthernetGeneric driver to lwip. But with some switches (e.g. cisco) there are problems with auto sense. But the main reason is that I want to limit the speed to 10mbits to save a lot of power.

greets traxanos

@earlephilhower
Copy link
Owner

I think a generic Ethernet class method would be a good way of doing this. This way it's integrated with the classes and we can implement the same logic, possibly, on other Ethernet adapters.

@earlephilhower earlephilhower added the enhancement New feature or request label Apr 15, 2024
@sstaub
Copy link
Contributor

sstaub commented Aug 13, 2024

I have this possibility in my Ethernet library https://github.com/sstaub/Ethernet3
Maybe that parts of the code will help to integrate it to lwip.

@earlephilhower
Copy link
Owner

Thanks! It's simple enough to do but because all the Ethernet (wired and wireless) are through the same base class here I was just cogitating on how to properly expose it so you can set 100M for wired or BG for wireless. An extensible enum like you use in your own wrapper sounds like a good way to get there...

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

No branches or pull requests

3 participants