1. 16 9月, 2009 1 次提交
  2. 03 8月, 2009 1 次提交
  3. 26 5月, 2009 1 次提交
  4. 19 4月, 2009 2 次提交
  5. 05 4月, 2009 1 次提交
  6. 04 4月, 2009 2 次提交
    • K
      [MTD] driver model updates (part 2) · 694bb7fc
      Kevin Cernekee 提交于
      1) Add more sysfs attributes: flags, size, erasesize, writesize,
         oobsize, numeraseregions, name
      
      2) Move core_initcall() code into init_mtd().  The original approach
         does not work if CONFIG_MTD=m .
      
      3) Add device_unregister() in del_mtd_device() so that devices get
         removed from sysfs as each driver is unloaded.
      Signed-off-by: NKevin Cernekee <kpc.mtd@gmail.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      694bb7fc
    • D
      [MTD] driver model updates · 1f24b5a8
      David Brownell 提交于
      Update driver model support in the MTD framework, so it fits
      better into the current udev-based hotplug framework:
      
       - Each mtd_info now has a device node.  MTD drivers should set
         the dev.parent field to point to the physical device, before
         setting up partitions or otherwise declaring MTDs.
      
       - Those device nodes always map to /sys/class/mtdX device nodes,
         which no longer depend on MTD_CHARDEV.
      
       - Those mtdX sysfs nodes have a "starter set" of attributes;
         it's not yet sufficient to replace /proc/mtd.
      
       - Enabling MTD_CHARDEV provides /sys/class/mtdXro/ nodes and the
         /sys/class/mtd*/dev attributes (for udev, mdev, etc).
      
       - Include a MODULE_ALIAS_CHARDEV_MAJOR macro.  It'll work with
         udev creating the /dev/mtd* nodes, not just a static rootfs.
      
      So the sysfs structure is pretty much what you'd expect, except
      that readonly chardev nodes are a bit quirky.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      1f24b5a8
  7. 24 3月, 2009 1 次提交
  8. 10 12月, 2008 1 次提交
    • A
      [MTD] update internal API to support 64-bit device size · 69423d99
      Adrian Hunter 提交于
      MTD internal API presently uses 32-bit values to represent
      device size.  This patch updates them to 64-bits but leaves
      the external API unchanged.  Extending the external API
      is a separate issue for several reasons.  First, no one
      needs it at the moment.  Secondly, whether the implementation
      is done with IOCTLs, sysfs or both is still debated.  Thirdly
      external API changes require the internal API to be accepted
      first.
      
      Note that although the MTD API will be able to support 64-bit
      device sizes, existing drivers do not and are not required
      to do so, although NAND base has been updated.
      
      In general, changing from 32-bit to 64-bit values cause little
      or no changes to the majority of the code with the following
      exceptions:
          	- printk message formats
          	- division and modulus of 64-bit values
          	- NAND base support
      	- 32-bit local variables used by mtdpart and mtdconcat
      	- naughtily assuming one structure maps to another
      	in MEMERASE ioctl
      Signed-off-by: NAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      69423d99
  9. 05 6月, 2008 4 次提交
  10. 03 2月, 2008 1 次提交
  11. 29 6月, 2007 1 次提交
  12. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  13. 30 11月, 2006 1 次提交
    • D
      [MTD] Use EXPORT_SYMBOL_GPL() for exported symbols. · dd36f267
      David Woodhouse 提交于
      While we're fixing up the newly-added symbol, change the neighbouring ones
      too, for consistency and also to reflect the author's interpretation of
      the GPL -- which is that _no_ non-GPL modules are permitted. The author
      always intended his code to be released under the GPL, and believes that
      any new interpretation of 'EXPORT_SYMBOL' as being any different from
      'EXPORT_SYMBOL_GPL' is entirely invalid; the GPL requires that _all_
      exports have the semantics of the new 'EXPORT_SYMBOL_GPL', which means the
      extra four characters are entirely redundant.
      
      But since those four extra characters trigger the check for illegal
      modules in a way that just EXPORT_SYMBOL does not, it's useful to change
      anyway. This action in no way indicates an admission that there is any
      legal distinction between the two states, and in particular does not
      indicate that the author believes that non-GPL modules may use symbols
      exported with EXPORT_SYMBOL alone.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      dd36f267
  14. 29 11月, 2006 3 次提交
  15. 22 9月, 2006 1 次提交
  16. 01 7月, 2006 1 次提交
  17. 14 6月, 2006 1 次提交
  18. 25 5月, 2006 1 次提交
  19. 01 4月, 2006 2 次提交
  20. 07 11月, 2005 2 次提交
  21. 23 5月, 2005 1 次提交
  22. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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