Home
last modified time | relevance | path

Searched hist:"334 ae614772b1147435dce9be3911f9040dff0d9" (Results 1 – 6 of 6) sorted by relevance

/openbmc/linux/drivers/sbus/
H A DMakefilediff 334ae614772b1147435dce9be3911f9040dff0d9 Wed Aug 27 19:01:57 CDT 2008 David S. Miller <davem@davemloft.net> sparc: Kill SBUS DVMA layer.

This thing was completely pointless.

Just find the OF device in the parent of drivers that want to program
this device, and map the DMA regs inside such drivers too.

This also moves the dummy claim_dma_lock() and release_dma_lock()
implementation to floppy_32.h, which makes it handle this issue
just like floppy_64.h does.

Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/arch/sparc/kernel/
H A Dsparc_ksyms.cdiff 334ae614772b1147435dce9be3911f9040dff0d9 Wed Aug 27 19:01:57 CDT 2008 David S. Miller <davem@davemloft.net> sparc: Kill SBUS DVMA layer.

This thing was completely pointless.

Just find the OF device in the parent of drivers that want to program
this device, and map the DMA regs inside such drivers too.

This also moves the dummy claim_dma_lock() and release_dma_lock()
implementation to floppy_32.h, which makes it handle this issue
just like floppy_64.h does.

Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/arch/sparc/include/asm/
H A Ddma.hdiff 334ae614772b1147435dce9be3911f9040dff0d9 Wed Aug 27 19:01:57 CDT 2008 David S. Miller <davem@davemloft.net> sparc: Kill SBUS DVMA layer.

This thing was completely pointless.

Just find the OF device in the parent of drivers that want to program
this device, and map the DMA regs inside such drivers too.

This also moves the dummy claim_dma_lock() and release_dma_lock()
implementation to floppy_32.h, which makes it handle this issue
just like floppy_64.h does.

Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dfloppy_32.hdiff 334ae614772b1147435dce9be3911f9040dff0d9 Wed Aug 27 19:01:57 CDT 2008 David S. Miller <davem@davemloft.net> sparc: Kill SBUS DVMA layer.

This thing was completely pointless.

Just find the OF device in the parent of drivers that want to program
this device, and map the DMA regs inside such drivers too.

This also moves the dummy claim_dma_lock() and release_dma_lock()
implementation to floppy_32.h, which makes it handle this issue
just like floppy_64.h does.

Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/scsi/
H A Desp_scsi.hdiff 334ae614772b1147435dce9be3911f9040dff0d9 Wed Aug 27 19:01:57 CDT 2008 David S. Miller <davem@davemloft.net> sparc: Kill SBUS DVMA layer.

This thing was completely pointless.

Just find the OF device in the parent of drivers that want to program
this device, and map the DMA regs inside such drivers too.

This also moves the dummy claim_dma_lock() and release_dma_lock()
implementation to floppy_32.h, which makes it handle this issue
just like floppy_64.h does.

Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dsun_esp.cdiff 334ae614772b1147435dce9be3911f9040dff0d9 Wed Aug 27 19:01:57 CDT 2008 David S. Miller <davem@davemloft.net> sparc: Kill SBUS DVMA layer.

This thing was completely pointless.

Just find the OF device in the parent of drivers that want to program
this device, and map the DMA regs inside such drivers too.

This also moves the dummy claim_dma_lock() and release_dma_lock()
implementation to floppy_32.h, which makes it handle this issue
just like floppy_64.h does.

Signed-off-by: David S. Miller <davem@davemloft.net>