1. 07 Dec, 2006 1 commit
  2. 06 Oct, 2006 1 commit
  3. 25 Sep, 2006 1 commit
  4. 31 Aug, 2006 1 commit
  5. 18 Aug, 2006 1 commit
    • Ben Dooks's avatar
      [ARM] 3753/1: S3C24XX: DMA fixes · f57e1abd
      Ben Dooks authored
      Patch from Ben Dooks
      A number of small issues with the S3C24XX DMA have
      cropped up, which this patch fixes. These are:
        - check wether we can load another buff in start
        - update state handling in s3c2410_dma_lastxfer
        - only reload in irq if channel is not idle
        - more informative timeout errors (add source)
        - do not call request_irq() with irqs locked
        - added waitforstop function
      The patch also adds a S3C2410_DMAOP_STARTED for
      the occasions when the driver wants to ensure that
      the DMA system load state is resynced after loading.
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
  6. 03 Jul, 2006 1 commit
  7. 30 Jun, 2006 1 commit
  8. 26 Jan, 2006 1 commit
  9. 23 Jul, 2005 1 commit
  10. 03 Jun, 2005 1 commit
    • Albrecht Dreß's avatar
      [PATCH] ARM: 2694/1: [s3c2410/dma] release irq properly to fix kernel oops · 105bb269
      Albrecht Dreß authored
      Patch from Albrecht Dre
      When a module requests a DMA channel via the function s3c2410_dma_request(), this function requests the appropriate irq under the name of the client module. When the client module is unloaded, it calls s3c2410_dma_free() which does not free the irq. Consequently, when e.g. running "cat /proc/interrupts", the irq owner points to freed memory, leading to a kernel oops.
      trivial, below
      Signed-off-by: Albrecht Dre
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
  11. 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!