1. 23 Jun, 2006 1 commit
  2. 26 May, 2006 1 commit
  3. 22 May, 2006 2 commits
    • Joern Engel's avatar
      [MTD] Introduce MTD_BIT_WRITEABLE · 5fa43394
      Joern Engel authored
      
      
      o Add a flag MTD_BIT_WRITEABLE for devices that allow single bits to be
        cleared.
      o Replace MTD_PROGRAM_REGIONS with a cleared MTD_BIT_WRITEABLE flag for
        STMicro and Intel Sibley flashes with internal ECC.  Those flashes
        disallow clearing of single bits, unlike regular NOR flashes, so the
        new flag models their behaviour better.
      o Remove MTD_ECC.  After the STMicro/Sibley merge, this flag is only set
        and never checked.
      Signed-off-by: default avatarJoern Engel <joern@wh.fh-wedel.de>
      5fa43394
    • Joern Engel's avatar
      [MTD] Merge STMicro NOR_ECC code with Intel Sibley code · c8b229de
      Joern Engel authored
      
      
      In 2002, STMicro started producing NOR flashes with internal ECC protection
      for small blocks (8 or 16 bytes).  Support for those flashes was added by me.
      In 2005, Intel Sibley flashes copied this strategy and Nico added support for
      those.  Merge the code for both.
      Signed-off-by: default avatarJoern Engel <joern@wh.fh-wedel.de>
      c8b229de
  4. 18 May, 2006 1 commit
    • David Woodhouse's avatar
      [JFFS2] Support new device nodes · aef9ab47
      David Woodhouse authored
      
      
      Device node major/minor numbers are just stored in the payload of a single
      data node. Just extend that to 4 bytes and use new_encode_dev() for it.
      
      We only use the 4-byte format if we _need_ to, if !old_valid_dev(foo).
      This preserves backwards compatibility with older code as much as
      possible. If we do make devices with major or minor numbers above 255, and
      then mount the file system with the old code, it'll just read the first
      two bytes and get the numbers wrong. If it comes to garbage-collect it,
      it'll then write back those wrong numbers. But that's about the best we
      can expect.
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      aef9ab47
  5. 13 May, 2006 1 commit
    • KaiGai Kohei's avatar
      [JFFS2][XATTR] XATTR support on JFFS2 (version. 5) · aa98d7cf
      KaiGai Kohei authored
      
      
      This attached patches provide xattr support including POSIX-ACL and
      SELinux support on JFFS2 (version.5).
      
      There are some significant differences from previous version posted
      at last December.
      The biggest change is addition of EBS(Erase Block Summary) support.
      Currently, both kernel and usermode utility (sumtool) can recognize
      xattr nodes which have JFFS2_NODETYPE_XATTR/_XREF nodetype.
      
      In addition, some bugs are fixed.
      - A potential race condition was fixed.
      - Unexpected fail when updating a xattr by same name/value pair was fixed.
      - A bug when removing xattr name/value pair was fixed.
      
      The fundamental structures (such as using two new nodetypes and exclusion
      mechanism by rwsem) are unchanged. But most of implementation were reviewed
      and updated if necessary.
      Espacially, we had to change several internal implementations related to
      load_xattr_datum() to avoid a potential race condition.
      
      [1/2] xattr_on_jffs2.kernel.version-5.patch
      [2/2] xattr_on_jffs2.utils.version-5.patch
      Signed-off-by: default avatarKaiGai Kohei <kaigai@ak.jp.nec.com>
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      aa98d7cf
  6. 28 Mar, 2006 1 commit
  7. 07 Nov, 2005 1 commit
  8. 06 Nov, 2005 5 commits
  9. 12 Jul, 2005 1 commit
  10. 06 Jul, 2005 1 commit
  11. 23 May, 2005 4 commits
  12. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4