-
Notifications
You must be signed in to change notification settings - Fork 7k
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
[TW#17970] LWIP update #1512
Comments
@zafrirron are you looking for a particular feature? |
Looking to port HomeKit protocol support github project that requires newer LWIP according to the project writer. |
Hi @zafrirron , the ESP32 has already supported Homekit, but it is not open on the github, you can send a request for ESP32 Homekit SDK on the ESP website. |
@FayeY don't close this too quickly. The SDK you are referring too is for MFI licensees only and Espressif has said to have no plans for a non-commercial SDK. So hobbyists are creating their own SDK for the ESP32. Since WWDC 2017 there is a Non-commercial HomeKit spec for Hobbyist, Enthusiasts, and prototyping without needing a license. People have already created an SDK for the ESP8266 (https://github.com/maximkulkin/esp-homekit). They want to port this to the ESP32, however, this can not be done due too LWIP being out of date and therefor missing features. So until Espressif decides to also open an SDK for non-commercial use, you should still consider updating LWIP |
Hi both, |
Same thing here. Trying to prototype something that needs newer features os LWIP. |
While you're at it, you could try to minimize the changes to upstream sources so that updating lwIP would be a simple matter of updating the sources and recompiling. lwIP tries to be compatible and/or simple to upgrade, so this should not be too hard as long as the sources are kept clean. Also: a) some of the local changes seem bogus and should not be required and b) for things that are real bugs, it would be nice to get them reported back to the lwIP project. |
@zafrirron@hchaudhary1@renssies@affonsoloyola@goldsimon |
That's great news! May I suggest again to work with the lwIP project (I'm the maintainer of that stack) to get you a clean copy of the stack? That will also make it easier to integrate new releases, as there should be no stability issues otherwise (when upgrading a clean lwIP stack). Just post your questions or issues to the lwip-devel@nongnu.org mailing list. |
@goldsimon yes, you are right ! we are doing what you said exactlly. |
i'm looking forward to the new lwip 2.0.3 version. |
I'm also waiting on this. Anything I can do to help? Thanks! |
Another bump (to show this would be appreciated). |
I would also like to see a sync to the upstream lwip. The esp-open-rtos has been following the upstream lwip and attempting to contribute changes upstream. It would make it easier to port code across these development environments. Is someone planning to work on this, or is it waiting for a contribution? |
Big +1 on this. I just spent the day finding and fixing a leak (LWIP Bug #51937) that has already been fixed "upstream". |
Attempt to fix espressif#1512 by upstreaming the library instead of a untracked copy
Attempt to fix espressif#1512 by upstreaming the library instead of a untracked copy
I've started a fork where i've removed Espressif's copy of LWIP in favour of using @goldsimon's version hosted on nongnu,org. The build does compile with "Copy L2 to L3" enabled under both LWIP and Ethernet component configuration options. Modifications have/are being done to components of ESP-IDF to support the new LWIP and I've found quite a few redundancies with developers reimplementing code that already exists in LWIP. Hopefully once it's all done, keeping LWIP up to date will be as easy as Please note that not all configuration options have been tested yet, but i hope to have that done in the next week. |
Big +1 on using clean upstream lwIP! |
@NZSmartie, using your fork! Thanks a ton! |
Hi all, sorry for replying later. |
Hi
Looking at LWIP version, you are using old version, lots of changes since you import LWIP,
would you consider updatating LWIP?
(not sure how many customizations done...)
The text was updated successfully, but these errors were encountered: