1. 21 Mar, 2019 1 commit
  2. 23 Feb, 2019 3 commits
    • Arnim Läuger's avatar
      DHT11 read sometimes failed with checksum error (#2679) · ebd147b3
      Arnim Läuger authored
      * DHT11 read sometimes failed with checksum error.
      
      The code assumed DHT11 devices only ever return zero in the temperature and humidity decimal fraction bytes. The datasheet doesn't guarantee this is the case, and by observation I have noticed that indeed the DHT11 may sometimes return another number, usually close to zero. This means that the code would fail with a checksum error, as the fraction bytes were not included when the checksum was calculated. These bytes are now taken into account and also returned as part of the measurement.
      
      This also means that the related dht.read() function is non-functional. If you have a DHT11 device that returns a non-zero decimal part, dht.read() will interpret it as a DHT22 result and return the wrong measurement. For this reason dht.read() should be retired. This patch does not address this issue.
      ebd147b3
    • ziggurat29's avatar
    • ziggurat29's avatar
      added MSVC project configuration for host-side tools (#2665) · 62789da0
      ziggurat29 authored
      Added MSVC project configuration (@ziggurat29) and support of MinGW (@TerryE) for host-side`luac.cross` tool
      62789da0
  3. 19 Feb, 2019 1 commit
  4. 17 Feb, 2019 1 commit
  5. 16 Feb, 2019 1 commit
  6. 14 Feb, 2019 1 commit
  7. 12 Feb, 2019 1 commit
    • ziggurat29's avatar
      Fix occasional luac.cross crash (#2661) · 0c7758a5
      ziggurat29 authored
      A block of memory is accessed after having been freed. This was obscured by the fact that 'oBuf' is a pointer into the middle of the block 'dynamicTables', so when dynamicTables is freed, oBuf is pointing to freed memory. Occasionally, luac.cross would crash because of this.
      0c7758a5
  8. 05 Feb, 2019 1 commit
  9. 02 Feb, 2019 1 commit
  10. 01 Feb, 2019 1 commit
  11. 24 Jan, 2019 1 commit
  12. 22 Jan, 2019 1 commit
  13. 20 Jan, 2019 1 commit
  14. 16 Jan, 2019 1 commit
    • galjonsfigur's avatar
      Updated FatFS from 0.12a to 0.13c (#2608) · 5d2bb87c
      galjonsfigur authored
      Files changed only by the author of FatFS (only updated to new version):
      
      - 00history.txt
      - 00readme.txt
      - ff.c
      - ff.h
      - ffunicode.c
      - diskio.h
      - integer.h
      - files in `option` folder except `syscall.c`
      
      Changes:
      - removed option folder (now everything is in ffunicode.c)
      - modified Makefile to support new version of FatFS
      - removed syscall.c and modified ffsystem.c from FatFS author instead
      - modified files: diskio.c, ffconf.h to mimic changes from new version
      - modified files: fatfs_config.h, myfatfs.c
      because of changes of configuration keywords in 0.13 version
      - removed empty lines from beginning of files:
      fatfs_prefix_lib.h, myfatfs.c, sdcard.c
      - changed version number in documentation
      5d2bb87c
  15. 15 Jan, 2019 2 commits
    • Nathaniel Wesley Filardo's avatar
      Update TLS protocol support (#2587) · 6e95d74f
      Nathaniel Wesley Filardo authored
      * Update TLS protocol support
      
      TLS1.0 is past PCI's EOL; BEAST is no more
      Enable elliptic curve key exchanges
      	Do not enable the smallest ECs for security
      	Do not enable the largest ECs for computational time
      	Do not enable 25519 (sad) because it doesn't go across the wire
      Drop non-PFS key exchanges
      Drop ARC4, Blowfish, DES, genprime, XTEA code
      Drop renegotiation support completely
      	It takes so much heap that it's not likely to work out well
      
      Tidy handling of SSL_BUFFER_SIZE
      
      Update docs
      Drop mention of startcom, since they are no more, for letsencrypt
      
      * Update mbedtls to 2.7.7
      
      Preserve our vsnprintf and platform hacks
      
      * Introduce TLS maximum fragment size knob
      
      Reduce buffer size to 4Ki by default and advertize that.  That's the
      largest we can advertize with the TLS MFL extension, so there's no
      point in making them larger.  The truly adventurous can re-raise
      SSL_BUFFER_SIZE and undefine the SSL_MAX_FRAGMENT_LENGTH_CODE and get
      back to the earlier behavior.
      
      * Default to mbedTLS debug with DEVELOP_VERSION
      6e95d74f
    • Javier Peletier's avatar
  16. 16 Dec, 2018 1 commit
    • andyleap's avatar
      Add set clock div (#2572) · 0a500eb9
      andyleap authored
      * Add spi.set_clock_div
      
      This will allow the SPI clock divider to be changed relatively simply,
      to better support multiple devices with varying SPI clock rate support
      
      * Add documentation
      0a500eb9
  17. 09 Dec, 2018 1 commit
  18. 05 Dec, 2018 1 commit
  19. 03 Dec, 2018 1 commit
  20. 30 Nov, 2018 1 commit
    • Johan Ström's avatar
      Handle large/chunked/fragmented MQTT messages properly (#2571) · 2d958750
      Johan Ström authored
      * MQTT: handle large/chunked/fragmented messages properly
      
      If a message spans multiple TCP packets it must be buffered before
      delivered to LUA. Prior code did not do this at all, so this "patch"
      really adds proper handling of fragmented MQTT packets.
      This could also occur if multiple small messages was sent in a
      single TCP packet, and the last message did not completely fit in that
      packet.
      
      Introduces a new option to the mqtt.Client constructor:
      max_publish_length which defaults to 1024
      
      Introduces a new 'overflow' callback.
      
      Fixes issue #2308 and proper fix for PR #2544.
      
      * mqtt.md: clarified heap allocation
      
      * mqtt: ensure ack is sent for overflowed publish
      
      If QoS is used we should still acknowledge that we received it, or server might retransmit it later.
      2d958750
  21. 28 Nov, 2018 1 commit
  22. 23 Nov, 2018 1 commit
  23. 16 Nov, 2018 1 commit
    • Carsten Elton Sørensen's avatar
      Calling vol:umount() would fail (#2558) · bb9a5977
      Carsten Elton Sørensen authored
      The volume returned by file.mount() could not be unmounted, because vol:umount() would fail with a cryptic error about the uncallable nature of the volume userdata object. This was due to the wrong metatable name being used for setting up the volume structure. The correct name, as registered elsewhere in file.c, is now used, and vol:umount() is callable.
      bb9a5977
  24. 13 Nov, 2018 2 commits
  25. 28 Oct, 2018 1 commit
  26. 24 Oct, 2018 1 commit
  27. 20 Oct, 2018 1 commit
  28. 19 Oct, 2018 1 commit
  29. 13 Oct, 2018 1 commit
    • Terry Ellison's avatar
      Optimise ROTable accesses and interface (#2505) · 5f67de8d
      Terry Ellison authored
      -  Optimise ROTable accesses and interface
      
      This includes some refinements to the ROTable cache which remove the linker cludges on the CROSS_COMPILE builds.  Also keyhole tweaks to some of the Lua VM code to implrove runtimes.
      
      I also noticed some compile time warnings during the build; the change to uz_unzip.c doesn't impact the compiled code, but does remove the compiler warnings.
      5f67de8d
  30. 10 Oct, 2018 1 commit
  31. 09 Oct, 2018 1 commit
  32. 07 Oct, 2018 1 commit
  33. 29 Sep, 2018 1 commit
  34. 21 Sep, 2018 1 commit
  35. 12 Sep, 2018 1 commit
  36. 27 Aug, 2018 1 commit