1. 15 Oct, 2012 18 commits
  2. 12 Oct, 2012 1 commit
  3. 08 Oct, 2012 10 commits
    • Tom Rini's avatar
      Prepare v2012.10-rc3 · c7c63221
      Tom Rini authored
      Signed-off-by: default avatarTom Rini <trini@ti.com>
      c7c63221
    • Albert ARIBAUD's avatar
      arm: armv7: omap3: Fix restore sequence in lowlevel_init · dec96689
      Albert ARIBAUD authored
      The restore sequence in lowlevel_init was in the wrong order,
      causing lr to lose its original value and be set equal to ip
      instead. Also, its use of the stack clashes with that of
      s_init, so move the s_init call after the restore and turn
      it  into a tail-optimized branch.
      Signed-off-by: default avatarAlbert ARIBAUD <albert.u.boot@aribaud.net>
      Tested-by: default avatarJeroen Hofstee <jeroen@myspectrum.nl>
      dec96689
    • Anatolij Gustschin's avatar
      yaffs2: Fix GCC 4.6 compile warnings · 8cc64baf
      Anatolij Gustschin authored
      Fix:
      yaffs_guts.c: In function 'yaffs_check_chunk_erased':
      yaffs_guts.c:324:6: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_guts.c: In function 'yaffs_verify_chunk_written':
      yaffs_guts.c:352:6: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_guts.c: In function 'yaffs_grab_chunk_cache':
      yaffs_guts.c:1488:6: warning: variable 'pushout' set but not used
      [-Wunused-but-set-variable]
      yaffs_guts.c: In function 'yaffs_check_obj_details_loaded':
      yaffs_guts.c:3180:6: warning: variable 'alloc_failed' set but not used
      [-Wunused-but-set-variable]
      yaffs_guts.c:3179:6: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_guts.c: In function 'yaffs_update_oh':
      yaffs_guts.c:3288:6: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_guts.c: In function 'yaffs_get_obj_name':
      yaffs_guts.c:4447:7: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_summary.c: In function 'yaffs_summary_read':
      yaffs_summary.c:194:6: warning: variable 'sum_tags_bytes' set but not
      used [-Wunused-but-set-variable]
      yaffs_verify.c: In function 'yaffs_verify_file':
      yaffs_verify.c:227:6: warning: variable 'actual_depth' set but not used
      [-Wunused-but-set-variable]
      yaffs_yaffs1.c: In function 'yaffs1_scan':
      yaffs_yaffs1.c:26:6: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_yaffs2.c: In function 'yaffs2_scan_chunk':
      yaffs_yaffs2.c:949:6: warning: variable 'result' set but not used
      [-Wunused-but-set-variable]
      yaffs_yaffs2.c: In function 'yaffs2_scan_backwards':
      yaffs_yaffs2.c:1352:6: warning: variable 'deleted' set but not used
      [-Wunused-but-set-variable]
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      Cc: Charles Manning <cdhmanning@gmail.com>
      Tested-by: default avatarAlbert ARIBAUD <albert.u.boot@aribaud.net>
      8cc64baf
    • Stephen Warren's avatar
      disk: part_dos: don't claim whole-disk FAT filesystems · d1efb644
      Stephen Warren authored
      Logically, a disk that contains a raw FAT filesystem does not in fact
      have a partition table. However, test_part_dos() was claiming that such
      disks did in fact have a DOS-style partition table. This caused
      get_device_and_partition() not to return a whole-disk disk_partition_t,
      since part_type != PART_TYPE_UNKNOWN.
      
      part_dos.c's print_partition_extended() detected the raw FAT filesystem
      condition and printed a fake partition table that encompassed the whole
      disk.
      
      However, part_dos.c's get_partition_info_extended() did not return any
      valid partitions in this case. This combination caused
      get_device_and_partition() not to find any valid partitions, and hence
      to return an error.
      
      Fix test_part_dos() not to claim that raw FAT filesystems are DOS
      partition tables. In turn, this causes get_device_and_partition() to
      return a whole-disk disk_partition_t, and hence the following commands
      work:
      
      fatls mmc 0 /
      fatls mmc 0:auto /
      
      An alternative would be to modify print_partition_extended() to detect
      raw FAT filesystems, just like print_partition_extended() does, and to
      return a fake partition in this case. However, this seems logically
      incorrect, and also duplicates code, since get_device_and_partition()
      falls back to returning a whole-disk partition when there is no partition
      table on the device.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      d1efb644
    • Stephen Warren's avatar
      FAT: check for partition 0 not 1 for whole-disk fs · bd1a7e30
      Stephen Warren authored
      The recent switch to use get_device_and_partition() from do_fat_ls()
      broke the ability to access a FAT filesystem directly on a whole device;
      FAT only works within a partition on a device.
      
      This change makes e.g. "fatls mmc 0:0" work; explicitly requesting
      partition ID 0 is something that get_device_and_partition() fully
      supports. However, fat_register_device() expects partition ID 1 to be
      used in the full-disk case; partition ID 1 was previously implicitly
      specified when the user didn't actually specify a partition ID. Update
      fat_register_device() to expect the correct ID.
      
      This change does imply that if a user explicitly executes "fatls mmc 0:1"
      then this will fail, and may be a change in behaviour.
      
      Note that this still prevents "fatls mmc 0:auto" from working. The next
      patch will fix that.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      bd1a7e30
    • Tetsuyuki Kobayashi's avatar
      arm: rmobile: bugfix: wrong register saving in lowlevel_init · 03eecab9
      Tetsuyuki Kobayashi authored
      lowlevel_init() of rmobile badly assumed that ip register holds return address.
      The commit "63ee53a7 armv7 cpu_init_crit: Simplify code" breaks this assumption.
      This patch removes this bad assumption and simplify code.
      Signed-off-by: default avatarTetsuyuki Kobayashi <koba@kmckk.co.jp>
      03eecab9
    • Luka Perkov's avatar
      ide: Correct IDE_BUS(dev) macro · 8a10180d
      Luka Perkov authored
      The IDE_BUS(dev) macro was previously doing dev >> 1.  This however is a
      mis-match of the usage in common/cmd_ide.c and would cause boards with
      multiple ports / devices to not correctly detect all devices.  For more
      details please see:
      http://lists.denx.de/pipermail/u-boot/2012-April/122525.html
      
      [Tom Rini: Reword commit message only]
      Tested-by: default avatarLuka Perkov <uboot@lukaperkov.net>
      Signed-off-by: default avatarSimon Baatz <gmbnomis@gmail.com>
      Signed-off-by: default avatarTom Rini <trini@ti.com>
      8a10180d
    • Laurence Withers's avatar
      GPIO: pca953x: fix error reporting · 633efe9c
      Laurence Withers authored
      Use the standard CMD_RET_* constants to clearly report errors from the
      pca953x command. In addition, print error messages when I2C communication
      fails.
      Signed-off-by: default avatarLaurence Withers <lwithers@guralp.com>
      633efe9c
    • Laurence Withers's avatar
      d75bc03f
    • Rommel Custodio's avatar
      ml507: Fix Xilinx uartlite driver hang · 6538397c
      Rommel Custodio authored
      The default configuration for ml507 will generate a hang() in the
      Xilinx uartlite driver.
      
      userial_ports[] in drivers/serial/serial_xuartlite.c does not get
      initialized properly. CONFIG_SERIAL_BASE is unused.
      XILINX_UARTLITE_BASEADDR is used instead.
      Signed-off-by: default avatarRommel Custodio <sessyargc+uboot@gmail.com>
      6538397c
  4. 05 Oct, 2012 6 commits
  5. 04 Oct, 2012 5 commits