09 May, 2007

1 commit


18 Feb, 2007

1 commit


13 Feb, 2007

1 commit


08 Feb, 2007

1 commit


08 Dec, 2006

1 commit

  • dma_is_consistent() is ill-designed in that it does not have a struct
    device pointer argument which makes proper support for systems that consist
    of a mix of coherent and non-coherent DMA devices hard. Change
    dma_is_consistent to take a struct device pointer as first argument and fix
    the sole caller to pass it.

    Signed-off-by: Ralf Baechle
    Cc: James Bottomley
    Cc: "David S. Miller"
    Cc: Greg KH
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ralf Baechle
     

23 Nov, 2006

1 commit


26 Apr, 2006

1 commit


02 Apr, 2006

1 commit

  • Patch from Lennert Buytenhek

    This patch adds support for the I/O coherent cache available on the
    xsc3. The approach is to provide a simple API to determine whether the
    chipset supports coherency by calling arch_is_coherent() and then
    setting the appropriate system memory PTE and PMD bits. In addition,
    we call this API on dma_alloc_coherent() and dma_map_single() calls.
    A generic version exists that will compile out all the coherency-related
    code that is not needed on the majority of ARM systems.

    Note that we do not check for coherency in the dma_alloc_writecombine()
    function as that still requires a special PTE setting. We also don't
    touch dma_mmap_coherent() as that is a special ARM-only API that is by
    definition only used on non-coherent system.

    Signed-off-by: Deepak Saxena
    Signed-off-by: Lennert Buytenhek
    Signed-off-by: Russell King

    Lennert Buytenhek
     

28 Oct, 2005

1 commit


17 Apr, 2005

2 commits

  • )

    From: Russell King

    The ARM dma_supported() is rather basic, and I don't think it takes into
    account everything that it should do (eg, whether the mask agrees with what
    we'd return for GFP_DMA allocations). Note this.

    Signed-off-by: Russell King
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    akpm@osdl.org
     
  • 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!

    Linus Torvalds