1. 14 May, 2014 20 commits
  2. 13 May, 2014 11 commits
  3. 12 May, 2014 9 commits
    • Michal Simek's avatar
      kbuild: Fix trailing whitespaces · 69c0d323
      Michal Simek authored
      Trivial fix.
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      69c0d323
    • Ian Campbell's avatar
      net/designware: call phy_connect_dev() to properly setup phylib device · 15e82e53
      Ian Campbell authored
      This sets up the linkage from the phydev back to the ethernet device. This
      symptom of not doing this which I noticed was:
          <NULL> Waiting for PHY auto negotiation to complete....
      rather than:
          dwmac.1c50000 Waiting for PHY auto negotiation to complete....
      Signed-off-by: default avatarIan Campbell <ijc@hellion.org.uk>
      Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
      15e82e53
    • Fabio Estevam's avatar
      boards.cfg: Keep entries sorted · 1b37fa83
      Fabio Estevam authored
      Run "tools/reformat.py -i -d '-' -s 8 <boards.cfg >boards0.cfg && mv boards0
      in order to keep the entries sorted.
      Signed-off-by: default avatarFabio Estevam <fabio.estevam@freescale.com>
      1b37fa83
    • Wu, Josh's avatar
      fs/fat: correct FAT16/12 file finding in root dir · dd6d7967
      Wu, Josh authored
      When write a file into FAT file system, it will search a match file in
      root dir. So the find_directory_entry() will get the first cluster of
      root dir content and search the directory item one by one. If the file
      is not found, we will call get_fatent_value() to get next cluster of root
      dir via lookup the FAT table and continue the search.
      
      The issue is in FAT16/12 system, we cannot get root dir's next clust
      from FAT table. The FAT table only be use to find the clust of data
      aera in FAT16/12.
      
      In FAT16/12 if the clust is in root dir, the clust number is a negative
      number or 0, 1. Since root dir is located in front of the data area.
      Data area start clust #2. So the root dir clust number should < 2.
      
      This patch will check above situation before call get_fatenv_value().
      If curclust is < 2, include minus number, we just increase one on the
      curclust since root dir is in continous cluster.
      
      The patch also add a sanity check for entry in get_fatenv_value().
      Signed-off-by: default avatarJosh Wu <josh.wu@atmel.com>
      dd6d7967
    • Wu, Josh's avatar
      fs: fat_write: fix the incorrect last cluster checking · 2e98f708
      Wu, Josh authored
      In fat_write.c, the last clust condition check is incorrect:
      
        if ((curclust >= 0xffffff8) || (curclust >= 0xfff8)) {
        	... ...
        }
      
      For example, in FAT32 if curclust is 0x11000. It is a valid clust.
      But on above condition check, it will be think as a last clust.
      
      So the correct last clust check should be:
        in fat32, curclust >= 0xffffff8
        in fat16, curclust >= 0xfff8
        in fat12, curclust >= 0xff8
      
      This patch correct the last clust check.
      Signed-off-by: default avatarJosh Wu <josh.wu@atmel.com>
      2e98f708
    • Wu, Josh's avatar
      fs/fat: add fat12 cluster check · 06118973
      Wu, Josh authored
      Signed-off-by: default avatarJosh Wu <josh.wu@atmel.com>
      06118973
    • Łukasz Majewski's avatar
      fs:ext4:write:fix: Reinitialize global variables after updating a file · 8b454eee
      Łukasz Majewski authored
      This bug shows up when file stored on the ext4 file system is updated.
      
      The ext4fs_delete_file() is responsible for deleting file's (e.g. uImage)
      data.
      However some global data (especially ext4fs_indir2_block), which is used
      during file deletion are left unchanged.
      
      The ext4fs_indir2_block pointer stores reference to old ext4 double
      indirect allocated blocks. When it is unchanged, after file deletion,
      ext4fs_write_file() uses the same pointer (since it is already initialized
      - i.e. not NULL) to return number of blocks to write. This trunks larger
      file when previous one was smaller.
      
      Lets consider following scenario:
      
      1. Flash target with ext4 formatted boot.img (which has uImage [*] on itself)
      2. Developer wants to upload their custom uImage [**]
      	- When new uImage [**] is smaller than the [*] - everything works
      	correctly - we are able to store the whole smaller file with corrupted
      	ext4fs_indir2_block pointer
      	- When new uImage [**] is larger than the [*] - theCRC is corrupted,
      	since truncation on data stored at eMMC was done.
      3. When uImage CRC error appears, then reboot and LTHOR/DFU reflashing causes
      	proper setting of ext4fs_indir2_block() and after that uImage[**]
      	is successfully stored (correct uImage [*] metadata is stored at an
      	eMMC on the first flashing).
      
      Due to above the bug was very difficult to reproduce.
      This patch sets default values for all ext4fs_indir* pointers/variables.
      Signed-off-by: default avatarLukasz Majewski <l.majewski@samsung.com>
      8b454eee
    • Łukasz Majewski's avatar
      fs:ext4:cleanup: Remove superfluous code · 35dd055b
      Łukasz Majewski authored
      Code responsible for handling situation when ext4 has block size of 1024B
      can be ordered to take less space.
      
      This patch does that for ext4 common and write files.
      Signed-off-by: default avatarLukasz Majewski <l.majewski@samsung.com>
      35dd055b
    • Steve Rae's avatar
      disk: part_efi: add support for the Backup GPT · ae95fad5
      Steve Rae authored
      Check the Backup GPT table if the Primary GPT table is invalid.
      Renamed "Secondary GPT" to "Backup GPT" as per:
        UEFI Specification (Version 2.3.1, Errata A)
      Signed-off-by: default avatarSteve Rae <srae@broadcom.com>
      ae95fad5