- 09 Jun, 2020 27 commits
-
-
Nathaniel Wesley Filardo authored
-
Nathaniel Wesley Filardo authored
-
Nathaniel Wesley Filardo authored
Seems more polite than quietly accepting other types as nil.
-
Nathaniel Wesley Filardo authored
-
Nathaniel Wesley Filardo authored
-
Nathaniel Wesley Filardo authored
* espconn: remove unused espconn code, take 1 This is the easiest part of https://github.com/nodemcu/nodemcu-firmware/issues/3004 . It removes a bunch of functions that were never called in our tree. * espconn: De-orbit espconn_gethostbyname Further work on https://github.com/nodemcu/nodemcu-firmware/issues/3004 While here, remove `mqtt`'s charming DNS-retry logic (which is neither shared with nor duplicated in other modules) and update its :connect() return value behavior and documentation. * espconn: remove scary global pktinfo A write-only global! How about that. * net: remove deprecated methods All the TLS stuff moved over there a long time ago, and net_createUDPSocket should just do what it says on the tin. * espconn_secure: remove ESPCONN_SERVER support We can barely function as a TLS client; being a TLS server seems like a real stretch. This code was never called from Lua anyway. * espconn_secure: more code removal * espconn_secure: simplify ssl options structure There is nothing "ssl_packet" about this structure. Get rid of the terrifying "pbuffer" pointer. Squash two structure types together and eliminate an unused field. * espconn_secure: refactor mbedtls_msg_info_load Split out espconn_mbedtls_parse, which we can use as part of our effort towards addressing https://github.com/nodemcu/nodemcu-firmware/issues/3032 * espconn_secure: introduce TLS cert/key callbacks The new feature part of https://github.com/nodemcu/nodemcu-firmware/issues/3032 Subsequent work will remove the old mechanism. * tls: add deprecation warnings * luacheck: net.ifinfo is a thing now * tls: remove use of espconn->reverse * mqtt: stop using espconn->reverse Instead, just place the espconn structure itself at the top of the user data. This enlarges the structure somewhat but removes one more layer of dynamic heap usage and NULL checks. While here, simplify the code a bit. * mqtt: remove redundant pointer to connect_info Everywhere we have the mqtt_state_t we also have the lmqtt_userdata. * mqtt: doc fixes * mqtt: note bug * tls: allow :on(...,nil) to unregister a callback
-
Nathaniel Wesley Filardo authored
* mqtt: expose "connfail" callback via :on() This makes it just like all the other callbacks in the module and is a revision of behavior called out in https://github.com/nodemcu/nodemcu-firmware/pull/2967 * mqtt: clarify when puback callback fires * mqtt: Don't reference stack buffers from the heap The confusingly-named "mqtt_connection_t" object is just a triple of - a serialized mqtt message pointer and length - a buffer pointer (to which the above can be written) - a message identifier The last of these must be passed around the mqtt state machine, but the first two are very local and the buffer is always sourced from the C stack. Unfortunately, because the entire structure is persisted in the heap, some callers assume that they can always use the structure without reinitialization (see mqtt_socket_close), which will trash the C stack. Sever the pairing between message id and local state, punt the local state entirely out of the heap, and rename things to be less confusing.
-
Nathaniel Wesley Filardo authored
Reserved words are always reserved in Lua, so let's not have people typing net["if"]...
-
galjonsfigur authored
-
Gregor Hartmann authored
-
M.K authored
-
Nikolay Fiykov authored
-
galjonsfigur authored
-
Lukáš Voborský authored
-
galjonsfigur authored
-
Nathaniel Wesley Filardo authored
* Remove app/include/netif/wlan_lwip_if.h This file appears to be unused in our tree. * New `net.if.info` call to show LwIP information This is a generalization of `wifi.sta`'s and `wifi.ap`'s `getip` and `getmac` calls. I don't propose to deprecate those, but perhaps we should, in the documentation, point users at this function instead. The direct motivation is to permit continued use of DHCP-provided NTP servers in a future where https://github.com/nodemcu/nodemcu-firmware/pull/2819 has landed, now that https://github.com/nodemcu/nodemcu-firmware/pull/2709 is in the tree. But rather than exposing just that information, a more general interface seems useful.
-
Marcel Stör authored
-
Gregor Hartmann authored
* clean effects library * Fix several issues in ws2812 and effects * Implement working way of calling shift from callback
-
Lukáš Voborský authored
-
Nathaniel Wesley Filardo authored
The internal implementation already preferentially forwards to the encoder module, so we should just remove these functions as they confuse people into thinking that we don't have their inverses (see the feature request https://github.com/nodemcu/nodemcu-firmware/issues/2907). Update the docs to refer to the encoder version and add deprecation warnings to the runtime implementations.
-
Marcel Stör authored
Fixes #2928, #2923
-
Marcel Stör authored
This reverts commit 32ad759409cbaaf53d3f51fc2f6573634eaadbc9.
-
Philip Gladstone authored
-
Terry Ellison authored
-
Terry Ellison authored
-
Terry Ellison authored
-
Terry Ellison authored
-
- 01 Aug, 2019 1 commit
-
-
Gregor Hartmann authored
-
- 27 Jul, 2019 7 commits
-
-
Nathaniel Wesley Filardo authored
* list_ref can become LUA_REFNIL, because that's what rawgeti returns for LUA_NOREF. Defensively guard for this, rather than falling into the sntp_dolookups loop with nil on the stack. * set_repeat_mode should not call itself, but should rather always do what it's going to do and then optionally do the rest if directed. * sntp_sync should not try to special case the single string argument: we should be queueing that name for DNS resolution, too. Towards that end, if we are given a single string, build a table and make that the list_ref and call off to sntp_dolookups, just like we otherwise do. FIXES: #2699
-
Gregor Hartmann authored
* Add DHCP option 42 / NTP * Update dhcp.c * resolve merge conflict * add lineend at end of file * fix merge conflict resolution error
-
Gregor authored
-
Gregor authored
-
Gregor authored
-
Gregor authored
-
Gregor authored
-
- 23 Jul, 2019 2 commits
-
-
Terry Ellison authored
-
Johny Mattsson authored
-
- 21 Jul, 2019 1 commit
-
-
Johny Mattsson authored
The PR removed the bulk of non-newlib headers from the NodeMCU source base. app/libc has now been cut down to the bare minimum overrides to shadow the corresponding functions in the SDK's libc. The old c_xyz.h headerfiles have been nuked in favour of the standard <xyz.h> headers, with a few exceptions over in sdk-overrides. Again, shipping a libc.a without headers is a terrible thing to do. We're still living on a prayer that libc was configured the same was as a default-configured xtensa gcc toolchain assumes it is. That part I cannot do anything about, unfortunately, but it's no worse than it has been before. This enables our source files to compile successfully using the standard header files, and use the typical malloc()/calloc()/realloc()/free(), the strwhatever()s and memwhatever()s. These end up, through macro and linker magic, mapped to the appropriate SDK or ROM functions.
-
- 16 Jul, 2019 1 commit
-
-
Nathaniel Wesley Filardo authored
* mqtt:connect() secure parameter should be boolean Continue to honor the old 0/1 values, but make them undocumented and add a deprecation warning to the code and docs. Eventually, this should go away. * mqtt: rip out deprecated autoreconnect * mqtt: expose all the callbacks via :on
-
- 14 Jul, 2019 1 commit
-
-
Gregor authored
-