1. 03 Jun, 2009 1 commit
  2. 29 May, 2009 2 commits
  3. 28 May, 2009 2 commits
    • Wolfgang Denk's avatar
    • Stefan Roese's avatar
      jffs2/mtdparts: Fix problem with usage from JFFS2 and MTDPARTS together · 76b5883d
      Stefan Roese authored
      Currently using JFFS2 with MTDPARTS enabled doesn't work. This is because
      mtdparts_init() is available in both files, cmd_mtdparts.c and
      cmd_jffs2.c. Please note that in the original cmd_jffs2.c file (before
      the jffs2/mtdparts command/file split those 2 different versions
      already existed. So this is nothing new. The main problem is that the
      variables "current_dev" and "current_partnum" are declared in both
      files now. This doesn't work.
      This patch now changes the names of those variable to more specific
      names: "current_mtd_dev" and "current_mtd_partnum". This is because
      this patch also changes the declaration from static to global, so
      that they can be used from both files.
      Please note that my first tests were not successful. The MTD devices
      selected via mtdparts are now accessed but I'm failing to see the
      directory listed via the "ls" command. Nothing is displayed. Perhaps
      I didn't generate the JFFS2 image correctly (I never used JFFS2 in
      U-Boot before). Not sure. Perhaps somebody else could take a look at
      this as well. I'll continue looking into this on Monday.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Detlev Zundel <dzu@denx.de>
      Cc: Ilya Yanok <yanok@emcraft.com>
      Cc: Renaud barbier <renaud.barbier@ge.com>
  4. 26 May, 2009 1 commit
  5. 23 May, 2009 3 commits
  6. 20 May, 2009 5 commits
  7. 19 May, 2009 1 commit
    • Graf Yang's avatar
      Blackfin: fix timer_init()/timer_reset() · ec01481d
      Graf Yang authored
      The timer_init() function was not using the right csync instruction, nor
      was it doing it right after disabling the core timer.
      The timer_reset() function would reset the timestamp, but not the actual
      timer, so there was a common edge case where get_timer() return a jump of
      one timestamp (couple milliseconds) right after resetting.  This caused
      many functions to improperly timeout right away.
      Signed-off-by: default avatarGraf Yang <graf.yang@analog.com>
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
  8. 16 May, 2009 3 commits
  9. 15 May, 2009 18 commits
  10. 12 May, 2009 1 commit
  11. 06 May, 2009 3 commits