1. 20 Apr, 2008 1 commit
  2. 18 Apr, 2008 1 commit
  3. 17 Apr, 2008 1 commit
  4. 15 Apr, 2008 4 commits
  5. 12 Apr, 2008 1 commit
  6. 28 Mar, 2008 2 commits
  7. 26 Mar, 2008 1 commit
  8. 24 Mar, 2008 1 commit
  9. 21 Mar, 2008 1 commit
  10. 20 Mar, 2008 2 commits
  11. 15 Mar, 2008 1 commit
  12. 13 Mar, 2008 2 commits
  13. 05 Mar, 2008 1 commit
  14. 04 Mar, 2008 3 commits
  15. 29 Feb, 2008 1 commit
  16. 28 Feb, 2008 1 commit
  17. 26 Feb, 2008 1 commit
  18. 23 Feb, 2008 3 commits
  19. 21 Feb, 2008 2 commits
  20. 18 Feb, 2008 1 commit
  21. 17 Feb, 2008 1 commit
  22. 14 Feb, 2008 2 commits
  23. 11 Feb, 2008 1 commit
  24. 09 Feb, 2008 1 commit
  25. 08 Feb, 2008 4 commits
    • Haavard Skinnemoen's avatar
      MAINTAINERS: add Haavard as maintainer of the atmel_serial driver · a1cfac48
      Haavard Skinnemoen authored
      The following patchset cleans up the atmel_serial driver a bit, moves a
      significant portion of the interrupt handler into a tasklet, and adds DMA
      support.  This is the result of a combined effort by Chip Coldwell, Remy
      Bohmer and me.  The patches should apply cleanly onto Linus' latest git tree,
      and I've also tested it on -mm (with a couple of avr32 fixes applied to make
      the rest of the tree compile.)
      
      With DMA, I see transfer rates around 92 kbps when transferring a big file
      using ZModem (both directions are roughly the same.) I've also tested the same
      thing with a bunch of debug options enabled.  The transfer rate is slightly
      lower, but no errors are reported.
      
      Note that break and error handling doesn't work too well with DMA enabled.
      This is a common problem with all the efforts I've seen adding DMA support to
      this driver (including my own).  The PDC error handling also accesses icount
      without locking.  I'm tempted to just ignore the problem for now and hopefully
      come up with a solution later.
      
      This patch:
      
      The atmel_serial driver never had a MAINTAINERS entry, although Andrew Victor
      has effectively been acting as a maintainer since he got the driver merged
      into mainline in the first place.
      
      I'll keep Cc'ing Andrew on all patches, but I'm going to take the main
      responsibility for getting things moving upstream from now on.
      Signed-off-by: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
      Acked-by: default avatarAndrew Victor <linux@maxim.org.za>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      a1cfac48
    • Jan Kara's avatar
      udf: change maintainer · 800fdfb9
      Jan Kara authored
      I've tried to contact Ben Fennema a few times but without success.  Since I'm
      currently probably closest to being an UDF maintainer, I guess it's fine to
      also change the entry in MAINTAINERS.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Cc: <bfennema@falcon.csc.calpoly.edu>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      800fdfb9
    • Nick Piggin's avatar
      rewrite rd · 9db5579b
      Nick Piggin authored
      This is a rewrite of the ramdisk block device driver.
      
      The old one is really difficult because it effectively implements a block
      device which serves data out of its own buffer cache.  It relies on the dirty
      bit being set, to pin its backing store in cache, however there are non
      trivial paths which can clear the dirty bit (eg.  try_to_free_buffers()),
      which had recently lead to data corruption.  And in general it is completely
      wrong for a block device driver to do this.
      
      The new one is more like a regular block device driver.  It has no idea about
      vm/vfs stuff.  It's backing store is similar to the buffer cache (a simple
      radix-tree of pages), but it doesn't know anything about page cache (the pages
      in the radix tree are not pagecache pages).
      
      There is one slight downside -- direct block device access and filesystem
      metadata access goes through an extra copy and gets stored in RAM twice.
      However, this downside is only slight, because the real buffercache of the
      device is now reclaimable (because we're not playing crazy games with it), so
      under memory intensive situations, footprint should effectively be the same --
      maybe even a slight advantage to the new driver because it can also reclaim
      buffer heads.
      
      The fact that it now goes through all the regular vm/fs paths makes it
      much more useful for testing, too.
      
         text    data     bss     dec     hex filename
         2837     849     384    4070     fe6 drivers/block/rd.o
         3528     371      12    3911     f47 drivers/block/brd.o
      
      Text is larger, but data and bss are smaller, making total size smaller.
      
      A few other nice things about it:
      - Similar structure and layout to the new loop device handlinag.
      - Dynamic ramdisk creation.
      - Runtime flexible buffer head size (because it is no longer part of the
        ramdisk code).
      - Boot / load time flexible ramdisk size, which could easily be extended
        to a per-ramdisk runtime changeable size (eg. with an ioctl).
      - Can use highmem for the backing store.
      
      [akpm@linux-foundation.org: fix build]
      [byron.bbradley@gmail.com: make rd_size non-static]
      Signed-off-by: default avatarNick Piggin <npiggin@suse.de>
      Signed-off-by: default avatarByron Bradley <byron.bbradley@gmail.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      9db5579b
    • David Howells's avatar
      mn10300: add the MN10300/AM33 architecture to the kernel · b920de1b
      David Howells authored
      Add architecture support for the MN10300/AM33 CPUs produced by MEI to the
      kernel.
      
      This patch also adds board support for the ASB2303 with the ASB2308 daughter
      board, and the ASB2305.  The only processor supported is the MN103E010, which
      is an AM33v2 core plus on-chip devices.
      
      [akpm@linux-foundation.org: nuke cvs control strings]
      Signed-off-by: default avatarMasakazu Urade <urade.masakazu@jp.panasonic.com>
      Signed-off-by: default avatarKoichi Yasutake <yasutake.koichi@jp.panasonic.com>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      b920de1b