1. 25 2月, 2010 4 次提交
  2. 11 2月, 2010 1 次提交
  3. 06 1月, 2010 1 次提交
  4. 02 1月, 2010 1 次提交
  5. 01 1月, 2010 14 次提交
  6. 16 12月, 2009 2 次提交
  7. 10 12月, 2009 1 次提交
  8. 07 12月, 2009 1 次提交
  9. 06 12月, 2009 1 次提交
  10. 04 12月, 2009 3 次提交
    • K
      mtd: Fix comment in Kconfig · 86185af9
      Krzysztof Halasa 提交于
      IXDP425 and Coyote aren't based on IXP2000 but on IXP425.
      Signed-off-by: NKrzysztof Halasa <khc@pm.waw.pl>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      86185af9
    • A
      tree-wide: fix assorted typos all over the place · af901ca1
      André Goddard Rosa 提交于
      That is "success", "unknown", "through", "performance", "[re|un]mapping"
      , "access", "default", "reasonable", "[con]currently", "temperature"
      , "channel", "[un]used", "application", "example","hierarchy", "therefore"
      , "[over|under]flow", "contiguous", "threshold", "enough" and others.
      Signed-off-by: NAndré Goddard Rosa <andre.goddard@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      af901ca1
    • S
      UBI: flush wl before clearing update marker · 6afaf8a4
      Sebastian Andrzej Siewior 提交于
      ubiupdatevol -t does the following:
      - ubi_start_update()
        - set_update_marker()
        - for all LEBs ubi_eba_unmap_leb()
        - clear_update_marker()
        - ubi_wl_flush()
      
      ubi_wl_flush() physically erases all PEB, once it returns all PEBs are
      empty. clear_update_marker() has the update marker written after return.
      If there is a power cut between the last two functions then the UBI
      volume has no longer the "update" marker set and may have some valid
      LEBs while some of them may be gone.
      If that volume in question happens to be a UBIFS volume, then mount
      will fail with
      
      |UBIFS error (pid 1361): ubifs_read_node: bad node type (255 but expected 6)
      |UBIFS error (pid 1361): ubifs_read_node: bad node at LEB 0:0
      |Not a node, first 24 bytes:
      |00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
      
      if there is at least one valid LEB and the wear-leveling worker managed
      to clear LEB 0.
      
      The patch waits for the wl worker to finish prior clearing the "update"
      marker on flash. The two new LEB which are scheduled for erasing after
      clear_update_marker() should not matter because they are only visible to
      UBI.
      Signed-off-by: NSebastian Andrzej Siewior <sebastian@breakpoint.cc>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Cc: stable@kernel.org
      6afaf8a4
  11. 01 12月, 2009 10 次提交
  12. 30 11月, 2009 1 次提交