1. 29 Dec, 2015 1 commit
  2. 28 Dec, 2015 3 commits
  3. 22 Dec, 2015 1 commit
  4. 21 Dec, 2015 3 commits
  5. 19 Dec, 2015 1 commit
  6. 18 Dec, 2015 4 commits
  7. 17 Dec, 2015 3 commits
  8. 16 Dec, 2015 5 commits
  9. 15 Dec, 2015 2 commits
  10. 14 Dec, 2015 2 commits
  11. 12 Dec, 2015 4 commits
    • Terry Ellison's avatar
      Merge pull request #804 from DiUS/panic · 0386ae65
      Terry Ellison authored
      Do not allow execution to continue after a PANIC
      0386ae65
    • 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
    • Johny Mattsson's avatar
      d84a24fc
    • Johny Mattsson's avatar
      Cleaned up all uses of INTERNAL_FLASH_START_ADDRESS. · c4e8b04f
      Johny Mattsson authored
      There was only one genuine use of this macro, all other places were
      using it only as a necessary compensation. While this was fine as long as
      it was the first meg of flash which was mapped, it became incorrect and
      quite dangerous whenever this assumption did not hold (such as when
      running from the second slot in an OTA scenario).
      
      The flash API now uses actual addresses, not translated/mapped
      addresses, and the users of this API have been adjusted accordingly.
      This makes the flash API work correctly regardless of what flash mapping
      is in use.
      
      The old macro is still available under the new name
      INTERNAL_FLASH_MAPPED_ADDRESS, and this is used to detect flash writes
      where the source is mapped flash (and thus has to be bounced), and to
      adjust the _flash_used_end linker symbol when used with
      flassh_find_sector() by the filesystem code. The latter usage is not
      OTA-proof, but in an OTA scenario the filesystem needs a fixed location
      anyway and thus would not use this code path.
      c4e8b04f
  12. 06 Dec, 2015 6 commits
  13. 05 Dec, 2015 3 commits
  14. 03 Dec, 2015 2 commits