Skip to content
Snippets Groups Projects
  1. Mar 26, 2012
  2. Feb 09, 2012
  3. Oct 19, 2011
    • Andres Salomon's avatar
      jffs2: add compr=lzo and compr=zlib options · 123005f3
      Andres Salomon authored
      
      ..to allow forcing of either compression scheme.  This will override
      compiled-in defaults.  jffs2_compress is reworked a bit, as the lzo/zlib
      override shares lots of code w/ the PRIORITY mode.
      
      v2: update show_options accordingly.
      
      Signed-off-by: default avatarAndres Salomon <dilinger@queued.net>
      Signed-off-by: default avatarArtem Bityutskiy <artem.bityutskiy@intel.com>
      123005f3
    • Andres Salomon's avatar
      jffs2: implement mount option parsing and compression overriding · 92abc475
      Andres Salomon authored
      
      Currently jffs2 has compile-time constants (and .config options)
      controlling whether or not the various compression/decompression
      drivers are built in and enabled.  This is fine for embedded
      systems, but it clashes with distribution kernels.  Distro kernels
      tend to turn on everything; this causes OpenFirmware to fall
      over, as it understands ZLIB-compressed inodes.  Booting a kernel
      that has LZO compression enabled, writing to the boot partition,
      and then rebooting causes OFW to fail to read the kernel from
      the filesystem.  This is because LZO compression has priority
      when writing new data to jffs2, if LZO is enabled.
      
      This patch adds mount option parsing, and a single supported
      option ("compr=none").  This adds the flexibility of being
      able to specify which compressor overrides on a per-superblock
      basis.  For now, we can simply disable compression;
      additional flexibility coming soon.
      
      v2: kill some printks, and implement show_options as suggested
      by Artem Bityutskiy.
      
      Signed-off-by: default avatarAndres Salomon <dilinger@queued.net>
      Signed-off-by: default avatarArtem Bityutskiy <artem.bityutskiy@intel.com>
      92abc475
  4. Oct 24, 2010
  5. Aug 08, 2010
  6. Dec 04, 2009
  7. Oct 17, 2008
  8. Jul 11, 2007
  9. Jul 10, 2007
  10. Apr 25, 2007
    • David Woodhouse's avatar
      [JFFS2] Tidy up licensing/copyright boilerplate. · c00c310e
      David Woodhouse authored
      
      In particular, remove the bit in the LICENCE file about contacting
      Red Hat for alternative arrangements. Their errant IS department broke
      that arrangement a long time ago -- the policy of collecting copyright
      assignments from contributors came to an end when the plug was pulled on
      the servers hosting the project, without notice or reason.
      
      We do still dual-license it for use with eCos, with the GPL+exception
      licence approved by the FSF as being GPL-compatible. It's just that nobody
      has the right to license it differently.
      
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      c00c310e
  11. Apr 02, 2007
  12. Jun 02, 2006
    • David Woodhouse's avatar
      [JFFS2] Remove stray __exit from jffs2_compressors_exit() · 3bcc86f5
      David Woodhouse authored
      
      It's used from the initfunc in case of failure too. We could actually do
      with an '__initexit' for this kind of thing -- when built in to the
      kernel, it could do with being dropped with the init text. We _could_
      actually just use __init for it, but that would break if/when we start
      dropping init text from modules. So let's just leave it as it was for now,
      and mutter a little more about random 'janitorial' fixes from people who
      aren't paying attention to what they're doing.
      
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      3bcc86f5
  13. May 16, 2006
  14. Nov 07, 2005
  15. Nov 06, 2005
  16. Apr 16, 2005
    • 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!
Loading