Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

2012-07-31 Thread cloudy.linux
Hi Phil On 2012-7-9 20:54, Phil Sutter wrote: Hi, On Sun, Jul 08, 2012 at 01:38:47PM +0800, cloudy.linux wrote: Newest result. Still couldn't boot up. This time the source was cloned from your git repository. MV-DMA: window at bar0: target 0, attr 14, base 0, size 800 MV-DMA: window

Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

2012-06-25 Thread cloudy.linux
On 2012-6-25 21:40, Phil Sutter wrote: Hi, On Wed, Jun 20, 2012 at 05:41:31PM +0200, Phil Sutter wrote: PS: I am currently working at the address decoding problem, will get back to in a few days when I have something to test. So stay tuned! I have updated the cesa-dma branch at

Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

2012-06-25 Thread cloudy.linux
On 2012-6-25 22:25, cloudy.linux wrote: On 2012-6-25 21:40, Phil Sutter wrote: Hi, On Wed, Jun 20, 2012 at 05:41:31PM +0200, Phil Sutter wrote: PS: I am currently working at the address decoding problem, will get back to in a few days when I have something to test. So stay tuned! I have

Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

2012-06-20 Thread cloudy.linux
Hi Phil On 2012-6-19 4:12, Simon Baatz wrote: I see one effect that I don't fully understand. Similar to the previous implementation, the system is mostly in kernel space when accessing an encrypted dm-crypt device: Today I also compiled the patched 3.5.0-rc3 for another NAS box with

Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

2012-06-19 Thread cloudy.linux
On 2012-6-19 19:51, Phil Sutter wrote: Hi Simon, On Mon, Jun 18, 2012 at 10:12:36PM +0200, Simon Baatz wrote: On Mon, Jun 18, 2012 at 03:47:18PM +0200, Phil Sutter wrote: On Sat, Jun 16, 2012 at 02:20:19AM +0200, Simon Baatz wrote: thanks for providing these patches; it's great to finally

Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

2012-06-19 Thread cloudy.linux
The CESA still didn't work as expected. But this time the machine managed to finish the boot. ... MV-DMA: IDMA engine up and running, IRQ 23 MV-DMA: idma_print_and_clear_irq: address miss @0! MV-DMA: tpg.reg + DMA_CTRL = 0x80001d04 MV-DMA: tpg.reg + DMA_BYTE_COUNT = 0x8010 MV-DMA: tpg.reg

Re: RFC: support for MV_CESA with IDMA or TDMA

2012-06-14 Thread cloudy.linux
On 2012-6-13 1:17, Phil Sutter wrote: Hi, The following patch series adds support for the TDMA engine built into Marvell's Kirkwood-based SoCs as well as the IDMA engine built into Marvell's Orion-based SoCs and enhances mv_cesa.c in order to use it for speeding up crypto operations. The

Re: RFC: support for MV_CESA with TDMA

2012-05-27 Thread cloudy.linux
On 2012-5-26 0:08, Phil Sutter wrote: Hi, The following patch series adds support for the TDMA engine built into Marvell's Kirkwood-based SoCs, and enhances mv_cesa.c in order to use it for speeding up crypto operations. Kirkwood hardware contains a security accelerator, which can control DMA

Re: [PATCH 2/4] mv_cesa: no need to write to that FPGA_INT_STATUS field

2012-05-27 Thread cloudy.linux
On 2012-5-25 21:54, Phil Sutter wrote: Also drop the whole definition, since it's unused otherwise. Signed-off-by: Phil Sutterphil.sut...@viprinet.com --- drivers/crypto/mv_cesa.c |1 - drivers/crypto/mv_cesa.h |7 --- 2 files changed, 0 insertions(+), 8 deletions(-) diff --git