Skip to content
Snippets Groups Projects
  1. Mar 16, 2016
    • John Crispin's avatar
      tools/flex: update to 2.6.1 · ae30ad61
      John Crispin authored
      
      Update flex to 2.6.1
      * Flex has moved to Github, adjust download link
      * Remove patch that has been applied upstream
      * Disable building tests to avoid circular dependency to bison
        - disable also docs and examples at the same time
      
      Signed-off-by: default avatarHannu Nyman <hannu.nyman@iki.fi>
      
      SVN-Revision: 49025
      ae30ad61
  2. Mar 10, 2016
  3. Mar 04, 2016
  4. Mar 03, 2016
  5. Feb 29, 2016
    • Felix Fietkau's avatar
      firmware-utils: mkfwimage: fix firmware_max_length for XM layout · 076d58d3
      Felix Fietkau authored
      
      The new u-boot version bundled with the 5.6.x firmwares from Ubiquiti gets
      confused by the smaller rootfs partition size; this can lead to various
      issues:
      
      1. We've gotten reports that flashing from the 5.6.x stock firmware to
         OpenWrt will brick devices; I wasn't able to reproduce this myself
      2. Flashing from 5.5.x stock firmware to OpenWrt and back to stock (via
         TFTP recovery), following by an update to 5.6.x via web interface can
         yield a bricked device with the following properties:
         - It can't be booted without entering commands over a serial console, as
           u-boot supplies the wrong MTD layout
         - The web interface won't accept any image with the original flash
           layout, so stock firmware upgrades are impossible
         - As the TFTP recovery doesn't update u-boot, returning to the old
           u-boot from firmware 5.5.x is impossible
      
      To recover from 2., creating an OpenWrt image which doesn't set u-boot as
      read-only and flashing a backup of the old u-boot from there is the only
      way known to me. (Fixing the mtdparts variable in u-boot-env from OpenWrt
      might also work; settings this from u-boot over serial didn't have
      any permanent effect.)
      
      Fix all of this by setting the correct flash layout also used by the stock
      firmware. Flashing has been tested from both firmware 5.5.x and 5.6.x. The
      fixed layout also matches the mtdparts defined by OpenWrt.
      
      Signed-off-by: default avatarMatthias Schiffer <mschiffer@universe-factory.net>
      
      SVN-Revision: 48829
      076d58d3
    • Felix Fietkau's avatar
      ar71xx, firmware-utils: split ubdev01 flash layout from XM · 619a58d6
      Felix Fietkau authored
      
      The ubdev01 profile defines its own MTDPARTS with smaller firmware
      partition, so give it its own UBNT_BOARD in mkfwimage.
      
      Signed-off-by: default avatarMatthias Schiffer <mschiffer@universe-factory.net>
      
      SVN-Revision: 48828
      619a58d6
    • Felix Fietkau's avatar
  6. Feb 12, 2016
  7. Feb 08, 2016
  8. Feb 01, 2016
    • Rafał Miłecki's avatar
      firmware-utils: add oseama tool for creating Seama entities · 590c7825
      Rafał Miłecki authored
      
      It has an important feature (compared to seama) of using multiple input
      files, aligning them and padding zeroes until reaching a specified
      absolute offset. This is needed for a proper flash layout on NAND. We
      want kernel partition to be big enough to handle future updates without
      a need to resize it and wipe whole "ubi" partition. It's important as
      we don't want to lose block counters.
      
      Signed-off-by: default avatarRafał Miłecki <zajec5@gmail.com>
      
      SVN-Revision: 48601
      590c7825
  9. Jan 28, 2016
    • Felix Fietkau's avatar
      tools/mkimage: backport SOURCE_DATE_EPOCH for reproducible builds · 37f09b81
      Felix Fietkau authored
      
      This pulls in Paul Kocialkowski's SOURCE_DATE_EPOCH support patch for u-boot,
      which landed upstream circa July 2015. Note that this "host" u-boot repo is
      only used to compile the 'mkimage' utility, and isn't used to actually compile
      a bootloader for any target.
      
      This patch could be removed if/when the host u-boot package is updated to a
      contemporary version (but there doesn't seem to be any motivation/need to do
      so).
      
      Signed-off-by: default avatarbryan newbold <bnewbold@robocracy.org>
      Signed-off-by: Felix Fietkau <nbd@openwrt.org> [fix portability error, refresh patches]
      
      SVN-Revision: 48542
      37f09b81
  10. Jan 21, 2016
  11. Jan 20, 2016
  12. Jan 18, 2016
  13. Jan 10, 2016
  14. Dec 23, 2015
  15. Dec 11, 2015
  16. Dec 10, 2015
  17. Dec 05, 2015
  18. Dec 02, 2015
  19. Nov 21, 2015
  20. Nov 13, 2015
  21. Nov 08, 2015
  22. Nov 07, 2015
    • Felix Fietkau's avatar
      tools/quilt: fix build error during kernel_menuconfig on a cleaned env · bdbd0dce
      Felix Fietkau authored
      
      When running "make kernel_menuconfig" right after "make clean", we error
      out with the following message:
      
      Makefile:22: recipe for target '.../build_dir/target-arm_cortex-a7_musl-1.1.10_eabi/linux-.../linux-3.18.18/.quilt_checked' failed
      make[2]: [.../build_dir/target-arm_cortex-a7_musl-1.1.10_eabi/linux-.../linux-3.18.18/.quilt_checked]
      Error 127 (ignored)
      
      The root cause of the problem is located in the OpenWrt specific quilt
      patch, which sets the quilt install directory to $STAGING_DIR/../host.
      However, on a clean environment (right after running "make clean"),
      $STAGING_DIR doesn't exist. The "quilt" executable doesn't find its
      different commands, errors out, and creates this message.
      
      We're fixing it by using $STAGING_DIR_HOST rather than $STAGING_DIR,
      which is absolute. It will work even if there is no target directory
      yet.
      
      Signed-off-by: default avatarMathieu Olivari <mathieu@codeaurora.org>
      Signed-off-by: default avatarFelix Fietkau <nbd@openwrt.org>
      
      SVN-Revision: 47410
      bdbd0dce
  23. Nov 06, 2015
  24. Nov 04, 2015
Loading