1. 05 Sep, 2016 2 commits
  2. 20 Mar, 2016 1 commit
  3. 11 Mar, 2016 1 commit
  4. 26 Feb, 2016 1 commit
    • TerryE's avatar
      Make the wifi.smart functions options and remove wofs and upgrade · 46ea2aa4
      TerryE authored
      AFAIK no one uses the wifi.startsmart() and wifi.stopsmart().  Removing
      them frees up an extra 20-25K of Flash to use as filesystem.  So I have
      added a new config define WIFI_SMART_ENABLE which is enabled by default
      so the default functionality is the same, but if this is commented out
      then this code is omitted.
      
      I have also removed wofs and upgrade from this build as we no longer
      support these.
      46ea2aa4
  5. 23 Jan, 2016 1 commit
  6. 23 Dec, 2015 1 commit
  7. 16 Dec, 2015 1 commit
    • Johny Mattsson's avatar
      Reworked module registration, removed modules.h · 4e8ef87d
      Johny Mattsson authored
      Module creation & registration now made a lot simpler. In essence,
      each module file is now self-contained and only needs a
      
        NODEMCU_MODULE(MYNAME, "myname", myname_map, luaopen_myname);
      
      line to both be automatically recognised by the Lua initialization
      as well as honor the LUA_USE_MODULES_MYNAME #define.
      4e8ef87d
  8. 12 Dec, 2015 1 commit
    • Johny Mattsson's avatar
      Major cleanup of module registration. · 6b6456be
      Johny Mattsson authored
      As per #810 & #796, only LUA_OPTIMIZE_MEMORY=2 & MIN_OPT_LEVEL=2 are
      supported when building. This commit effects that limitation.
      
      With this change modules/auxmods.h no longer needs to be updated for
      every new module, nor do module writers need to cater for a hypothetical
      LUA_OPTIMIZE_MEMORY < 2 scenario.
      6b6456be
  9. 05 Dec, 2015 1 commit
    • Nick Andrew's avatar
      Remove the lobject.c:88 assertion failures · e9ee9a57
      Nick Andrew authored
      
      
      When lua assertions are enabled, normal operation results in many:
      
      lobject.c:88: (((t1)->tt) == 4)
      lobject.c:88: (((t2)->tt) == 4)
      lobject.c:88: (((t1)->tt) == 4)
      lobject.c:88: (((t2)->tt) == 4)
      lobject.c:88: (((t1)->tt) == 4)
      lobject.c:88: (((t2)->tt) == 4)
      
      It comes from using the pvalue() macro for 3 pointer types, where
      pvalue() also checks the type of pointer and complains through the
      assertion where the type == 4 (TLIGHTUSERDATA).
      
      Use the correct macro according to the type of data being compared
      to eliminate this assertion error.
      Signed-off-by: default avatarNick Andrew <nick@nick-andrew.net>
      e9ee9a57
  10. 03 Dec, 2015 1 commit
  11. 01 Dec, 2015 1 commit
  12. 22 Nov, 2015 1 commit
  13. 18 Nov, 2015 1 commit
  14. 08 Nov, 2015 1 commit
  15. 03 Nov, 2015 3 commits
  16. 12 Oct, 2015 3 commits
  17. 05 Apr, 2015 1 commit
  18. 14 Mar, 2015 1 commit
  19. 06 Mar, 2015 3 commits
  20. 01 Mar, 2015 1 commit
  21. 14 Feb, 2015 1 commit
  22. 13 Feb, 2015 3 commits
  23. 12 Feb, 2015 1 commit
  24. 11 Feb, 2015 1 commit
  25. 26 Jan, 2015 1 commit
  26. 25 Jan, 2015 1 commit
  27. 24 Jan, 2015 1 commit
  28. 07 Jan, 2015 1 commit
  29. 06 Jan, 2015 1 commit
  30. 05 Jan, 2015 2 commits