Thread: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
Brought to you by:
david-m
Menu
▾
▴
ocf-linux-users
|
From: Flaig, P. <Pat...@bd...> - 2010-08-02 14:47:39
|
Hello, Maybe someone can help me; I'm getting some compile errors when trying to compile the OCF driver for Marvell Kirkwood. I'm using a Kernel 2.6.31.14 with the latest OCF patches (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross compilers (arm-mv5vfp-linux-gnueabi). OCF without this driver enabled compiles without any problems. Here is the output of the build process: make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage scripts/kconfig/conf -s arch/arm/Kconfig CHK include/linux/version.h make[1]: `include/asm-arm/mach-types.h' is up to date. CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-arm CALL scripts/checksyscalls.sh <stdin>:1351:2: warning: #warning syscall migrate_pages not implemented <stdin>:1407:2: warning: #warning syscall pselect6 not implemented <stdin>:1411:2: warning: #warning syscall ppoll not implemented <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented CHK include/linux/compile.h CC crypto/ocf/kirkwood/cesa/mvCesa.o CC crypto/ocf/kirkwood/cesa/mvLru.o CC crypto/ocf/kirkwood/cesa/mvMD5.o CC crypto/ocf/kirkwood/cesa/mvSHA1.o CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: mvAesBoxes.dat: No such file or directory crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared identifier is reported only once crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each function it appears in.) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared (first use in this function) crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared (first use in this function) make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 make[2]: *** [crypto/ocf/kirkwood] Error 2 make[1]: *** [crypto/ocf] Error 2 make: *** [crypto] Error 2 I was able to add the missing mvAesBoxes.dat(from the original Marvell Kirkwood kernel), but still some compile errors. make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage CHK include/linux/version.h make[1]: `include/asm-arm/mach-types.h' is up to date. CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-arm CALL scripts/checksyscalls.sh <stdin>:1351:2: warning: #warning syscall migrate_pages not implemented <stdin>:1407:2: warning: #warning syscall pselect6 not implemented <stdin>:1411:2: warning: #warning syscall ppoll not implemented <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented CHK include/linux/compile.h CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' expects type 'long int', but argument 4 has type 'unsigned int' crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' expects type 'long int', but argument 4 has type 'unsigned int' crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' expects type 'long int', but argument 5 has type 'unsigned int' crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' expects type 'long int', but argument 3 has type 'unsigned int' crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' expects type 'long int', but argument 2 has type 'unsigned int' crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' expects type 'long int', but argument 2 has type 'unsigned int' CC crypto/ocf/kirkwood/cesa_ocf_drv.o crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No such file or directory crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration of function 'crypto_copy_bits_back' crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing pointer to incomplete type crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing pointer to incomplete type crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing pointer to incomplete type crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' expects type 'unsigned int', but argument 4 has type 'void *' crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization from incompatible pointer type make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 make[2]: *** [crypto/ocf/kirkwood] Error 2 make[1]: *** [crypto/ocf] Error 2 make: *** [crypto] Error 2 Any help or support is welcome :) Thanks and regards. Patrick |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-02 15:26:00
|
Hi, Thanks for the hint, but where should this file or the directory "plat" be? Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? But when it is the same, why is it included twice <cesa/mv_cesa.h> and <plat/mv_cesa.h> Patrick -----Original Message----- From: added by portage for apache [mailto:ap...@at...] On Behalf Of md...@as... Sent: Monday, August 02, 2010 4:59 PM To: Flaig, Patrick Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Hi Ignore the warnings make sure that the following file exists and you include it: plat/mv_cesa.h >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No >> such file >>or directory Regards Mihalis Quoting "Flaig, Patrick" <Pat...@bd...>: > Hello, > > Maybe someone can help me; I'm getting some compile errors when > trying to compile the OCF driver for Marvell Kirkwood. > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > compilers (arm-mv5vfp-linux-gnueabi). > > OCF without this driver enabled compiles without any problems. > > Here is the output of the build process: > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > scripts/kconfig/conf -s arch/arm/Kconfig > CHK include/linux/version.h > make[1]: `include/asm-arm/mach-types.h' is up to date. > CHK include/linux/utsrelease.h > SYMLINK include/asm -> include/asm-arm > CALL scripts/checksyscalls.sh > <stdin>:1351:2: warning: #warning syscall migrate_pages not > implemented > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > CHK include/linux/compile.h > CC crypto/ocf/kirkwood/cesa/mvCesa.o > CC crypto/ocf/kirkwood/cesa/mvLru.o > CC crypto/ocf/kirkwood/cesa/mvMD5.o > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > mvAesBoxes.dat: No such file or directory > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' undeclared > (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > identifier is reported only once > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each function > it appears in.) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > undeclared (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > (first use in this function) > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > (first use in this function) > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > make[2]: *** [crypto/ocf/kirkwood] Error 2 > make[1]: *** [crypto/ocf] Error 2 > make: *** [crypto] Error 2 > > I was able to add the missing mvAesBoxes.dat(from the original > Marvell Kirkwood kernel), but still some compile errors. > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > CHK include/linux/version.h > make[1]: `include/asm-arm/mach-types.h' is up to date. > CHK include/linux/utsrelease.h > SYMLINK include/asm -> include/asm-arm > CALL scripts/checksyscalls.sh > <stdin>:1351:2: warning: #warning syscall migrate_pages not > implemented > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > CHK include/linux/compile.h > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > expects type 'long int', but argument 4 has type 'unsigned int' > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > expects type 'long int', but argument 4 has type 'unsigned int' > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > expects type 'long int', but argument 5 has type 'unsigned int' > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > expects type 'long int', but argument 3 has type 'unsigned int' > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > expects type 'long int', but argument 2 has type 'unsigned int' > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > expects type 'long int', but argument 2 has type 'unsigned int' > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > such file or directory > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > of function 'crypto_copy_bits_back' > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > pointer to incomplete type > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > pointer to incomplete type > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > pointer to incomplete type > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > expects type 'unsigned int', but argument 4 has type 'void *' > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > from incompatible pointer type > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > make[2]: *** [crypto/ocf/kirkwood] Error 2 > make[1]: *** [crypto/ocf] Error 2 > make: *** [crypto] Error 2 > > Any help or support is welcome :) > > Thanks and regards. > > Patrick > |
|
From: David M. <dav...@mc...> - 2010-08-03 02:40:36
|
Jivin Flaig, Patrick lays it down ... > Hi, > > Thanks for the hint, but where should this file or the directory "plat" be? > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > But when it is the same, why is it included twice <cesa/mv_cesa.h> and <plat/mv_cesa.h> I think that plat/mv_cesa.h comes from the linux kernel. Cheers, Davidm > -----Original Message----- > From: added by portage for apache [mailto:ap...@at...] On Behalf Of md...@as... > Sent: Monday, August 02, 2010 4:59 PM > To: Flaig, Patrick > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > Hi > Ignore the warnings > make sure that the following file exists and you include it: plat/mv_cesa.h > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > >> such file >>or directory > Regards > Mihalis > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > Hello, > > > > Maybe someone can help me; I'm getting some compile errors when > > trying to compile the OCF driver for Marvell Kirkwood. > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > compilers (arm-mv5vfp-linux-gnueabi). > > > > OCF without this driver enabled compiles without any problems. > > > > Here is the output of the build process: > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > scripts/kconfig/conf -s arch/arm/Kconfig > > CHK include/linux/version.h > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > CHK include/linux/utsrelease.h > > SYMLINK include/asm -> include/asm-arm > > CALL scripts/checksyscalls.sh > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > implemented > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > CHK include/linux/compile.h > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > mvAesBoxes.dat: No such file or directory > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' undeclared > > (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > identifier is reported only once > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each function > > it appears in.) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > (first use in this function) > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > make[1]: *** [crypto/ocf] Error 2 > > make: *** [crypto] Error 2 > > > > I was able to add the missing mvAesBoxes.dat(from the original > > Marvell Kirkwood kernel), but still some compile errors. > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > CHK include/linux/version.h > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > CHK include/linux/utsrelease.h > > SYMLINK include/asm -> include/asm-arm > > CALL scripts/checksyscalls.sh > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > implemented > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > CHK include/linux/compile.h > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > expects type 'long int', but argument 4 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > expects type 'long int', but argument 4 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > expects type 'long int', but argument 5 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > expects type 'long int', but argument 3 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > expects type 'long int', but argument 2 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > expects type 'long int', but argument 2 has type 'unsigned int' > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > such file or directory > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > of function 'crypto_copy_bits_back' > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > pointer to incomplete type > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > pointer to incomplete type > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > pointer to incomplete type > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > expects type 'unsigned int', but argument 4 has type 'void *' > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > from incompatible pointer type > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > make[1]: *** [crypto/ocf] Error 2 > > make: *** [crypto] Error 2 > > > > Any help or support is welcome :) > > > > Thanks and regards. > > > > Patrick > > > > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Ocf-linux-users mailing list > Ocf...@li... > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-03 06:22:16
|
Hi, but that makes no sense, the mv_cesa.h is already included in the cesa_ocf_driver.c (#include <cesa/mv_cesa.h>). Why should including it twice solve the problem? If I comment out the #include <plat/mv_cesa.h>, I'm getting the next problem: crypto_copy_bits_back is not defined but used in the code. Regards Patrick -----Ursprüngliche Nachricht----- Von: Michalis Digas [mailto:md...@as...] Gesendet: Montag, 2. August 2010 18:28 An: Flaig, Patrick Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Hi Make a directory "plat" in kernels include folder and through the file there Mihalis On 2/8/2010 17:25, Flaig, Patrick wrote: > Hi, > > Thanks for the hint, but where should this file or the directory "plat" be? > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > But when it is the same, why is it included twice<cesa/mv_cesa.h> and<plat/mv_cesa.h> > > Patrick > > -----Original Message----- > From: added by portage for apache [mailto:ap...@at...] On Behalf Of md...@as... > Sent: Monday, August 02, 2010 4:59 PM > To: Flaig, Patrick > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > Hi > Ignore the warnings > make sure that the following file exists and you include it: plat/mv_cesa.h >>> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No >>> such file>>or directory > Regards > Mihalis > > Quoting "Flaig, Patrick"<Pat...@bd...>: > >> Hello, >> >> Maybe someone can help me; I'm getting some compile errors when >> trying to compile the OCF driver for Marvell Kirkwood. >> >> I'm using a Kernel 2.6.31.14 with the latest OCF patches >> (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross >> compilers (arm-mv5vfp-linux-gnueabi). >> >> OCF without this driver enabled compiles without any problems. >> >> Here is the output of the build process: >> >> make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage >> scripts/kconfig/conf -s arch/arm/Kconfig >> CHK include/linux/version.h >> make[1]: `include/asm-arm/mach-types.h' is up to date. >> CHK include/linux/utsrelease.h >> SYMLINK include/asm -> include/asm-arm >> CALL scripts/checksyscalls.sh >> <stdin>:1351:2: warning: #warning syscall migrate_pages not >> implemented >> <stdin>:1407:2: warning: #warning syscall pselect6 not implemented >> <stdin>:1411:2: warning: #warning syscall ppoll not implemented >> <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented >> CHK include/linux/compile.h >> CC crypto/ocf/kirkwood/cesa/mvCesa.o >> CC crypto/ocf/kirkwood/cesa/mvLru.o >> CC crypto/ocf/kirkwood/cesa/mvMD5.o >> CC crypto/ocf/kirkwood/cesa/mvSHA1.o >> CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: >> mvAesBoxes.dat: No such file or directory >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' undeclared >> (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared >> identifier is reported only once >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each function >> it appears in.) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared >> (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' >> undeclared (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared >> (first use in this function) >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': >> crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared >> (first use in this function) >> make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 >> make[2]: *** [crypto/ocf/kirkwood] Error 2 >> make[1]: *** [crypto/ocf] Error 2 >> make: *** [crypto] Error 2 >> >> I was able to add the missing mvAesBoxes.dat(from the original >> Marvell Kirkwood kernel), but still some compile errors. >> >> make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage >> CHK include/linux/version.h >> make[1]: `include/asm-arm/mach-types.h' is up to date. >> CHK include/linux/utsrelease.h >> SYMLINK include/asm -> include/asm-arm >> CALL scripts/checksyscalls.sh >> <stdin>:1351:2: warning: #warning syscall migrate_pages not >> implemented >> <stdin>:1407:2: warning: #warning syscall pselect6 not implemented >> <stdin>:1411:2: warning: #warning syscall ppoll not implemented >> <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented >> CHK include/linux/compile.h >> CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o >> CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o >> CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' >> expects type 'long int', but argument 4 has type 'unsigned int' >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' >> expects type 'long int', but argument 4 has type 'unsigned int' >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' >> expects type 'long int', but argument 5 has type 'unsigned int' >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' >> expects type 'long int', but argument 3 has type 'unsigned int' >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' >> expects type 'long int', but argument 2 has type 'unsigned int' >> crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' >> expects type 'long int', but argument 2 has type 'unsigned int' >> CC crypto/ocf/kirkwood/cesa_ocf_drv.o >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No >> such file or directory >> crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': >> crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration >> of function 'crypto_copy_bits_back' >> crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': >> crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing >> pointer to incomplete type >> crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing >> pointer to incomplete type >> crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing >> pointer to incomplete type >> crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': >> crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' >> expects type 'unsigned int', but argument 4 has type 'void *' >> crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: >> crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization >> from incompatible pointer type >> make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 >> make[2]: *** [crypto/ocf/kirkwood] Error 2 >> make[1]: *** [crypto/ocf] Error 2 >> make: *** [crypto] Error 2 >> >> Any help or support is welcome :) >> >> Thanks and regards. >> >> Patrick >> > > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Ocf-linux-users mailing list > Ocf...@li... > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-03 06:30:12
|
Hi, the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. So I think I have to fix this first to continue with porting the driver. Patrick -----Ursprüngliche Nachricht----- Von: David McCullough [mailto:dav...@mc...] Gesendet: Dienstag, 3. August 2010 02:58 An: Flaig, Patrick Cc: ocf...@li... Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Jivin Flaig, Patrick lays it down ... > Hi, > > Thanks for the hint, but where should this file or the directory "plat" be? > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > But when it is the same, why is it included twice <cesa/mv_cesa.h> and <plat/mv_cesa.h> I think that plat/mv_cesa.h comes from the linux kernel. Cheers, Davidm > -----Original Message----- > From: added by portage for apache [mailto:ap...@at...] On Behalf Of md...@as... > Sent: Monday, August 02, 2010 4:59 PM > To: Flaig, Patrick > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > Hi > Ignore the warnings > make sure that the following file exists and you include it: plat/mv_cesa.h > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > >> such file >>or directory > Regards > Mihalis > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > Hello, > > > > Maybe someone can help me; I'm getting some compile errors when > > trying to compile the OCF driver for Marvell Kirkwood. > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > compilers (arm-mv5vfp-linux-gnueabi). > > > > OCF without this driver enabled compiles without any problems. > > > > Here is the output of the build process: > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > scripts/kconfig/conf -s arch/arm/Kconfig > > CHK include/linux/version.h > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > CHK include/linux/utsrelease.h > > SYMLINK include/asm -> include/asm-arm > > CALL scripts/checksyscalls.sh > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > implemented > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > CHK include/linux/compile.h > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > mvAesBoxes.dat: No such file or directory > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' undeclared > > (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > identifier is reported only once > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each function > > it appears in.) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > undeclared (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > (first use in this function) > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > (first use in this function) > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > make[1]: *** [crypto/ocf] Error 2 > > make: *** [crypto] Error 2 > > > > I was able to add the missing mvAesBoxes.dat(from the original > > Marvell Kirkwood kernel), but still some compile errors. > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > CHK include/linux/version.h > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > CHK include/linux/utsrelease.h > > SYMLINK include/asm -> include/asm-arm > > CALL scripts/checksyscalls.sh > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > implemented > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > CHK include/linux/compile.h > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > expects type 'long int', but argument 4 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > expects type 'long int', but argument 4 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > expects type 'long int', but argument 5 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > expects type 'long int', but argument 3 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > expects type 'long int', but argument 2 has type 'unsigned int' > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > expects type 'long int', but argument 2 has type 'unsigned int' > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > such file or directory > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > of function 'crypto_copy_bits_back' > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > pointer to incomplete type > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > pointer to incomplete type > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > pointer to incomplete type > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > expects type 'unsigned int', but argument 4 has type 'void *' > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > from incompatible pointer type > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > make[1]: *** [crypto/ocf] Error 2 > > make: *** [crypto] Error 2 > > > > Any help or support is welcome :) > > > > Thanks and regards. > > > > Patrick > > > > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Ocf-linux-users mailing list > Ocf...@li... > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: David M. <dav...@mc...> - 2010-08-03 09:40:50
Attachments:
mv_cesa.h
marvel.diff
|
Jivin Flaig, Patrick lays it down ... > Hi, > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > So I think I have to fix this first to continue with porting the driver. A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. Also a patch the was not in the last release which will fix the copyback errors you were seeing. Cheers, Davidm > -----Urspr??ngliche Nachricht----- > Von: David McCullough [mailto:dav...@mc...] > Gesendet: Dienstag, 3. August 2010 02:58 > An: Flaig, Patrick > Cc: ocf...@li... > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi, > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> and <plat/mv_cesa.h> > > I think that plat/mv_cesa.h comes from the linux kernel. > > Cheers, > Davidm > > > -----Original Message----- > > From: added by portage for apache [mailto:ap...@at...] On Behalf Of md...@as... > > Sent: Monday, August 02, 2010 4:59 PM > > To: Flaig, Patrick > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > > > Hi > > Ignore the warnings > > make sure that the following file exists and you include it: plat/mv_cesa.h > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > >> such file >>or directory > > Regards > > Mihalis > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > Hello, > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > Here is the output of the build process: > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > mvAesBoxes.dat: No such file or directory > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > identifier is reported only once > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each function > > > it appears in.) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > (first use in this function) > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > such file or directory > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > of function 'crypto_copy_bits_back' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > from incompatible pointer type > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > Any help or support is welcome :) > > > > > > Thanks and regards. > > > > > > Patrick > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://p.sf.net/sfu/dev2dev-palm > > _______________________________________________ > > Ocf-linux-users mailing list > > Ocf...@li... > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-03 12:30:35
|
Hi David, Thanks, for the files, now I'm able to compile the driver. When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. One comment from me, I think in the current release mvAesBoxes.dat is also missing. Is there a next release planned with fixes for the issues we found? Patrick -----Original Message----- From: David McCullough [mailto:dav...@mc...] Sent: Tuesday, August 03, 2010 11:39 AM To: Flaig, Patrick Cc: ocf...@li... Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Jivin Flaig, Patrick lays it down ... > Hi, > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > So I think I have to fix this first to continue with porting the driver. A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. Also a patch the was not in the last release which will fix the copyback errors you were seeing. Cheers, Davidm > -----Urspr??ngliche Nachricht----- > Von: David McCullough [mailto:dav...@mc...] > Gesendet: Dienstag, 3. August 2010 02:58 > An: Flaig, Patrick > Cc: ocf...@li... > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi, > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> > > and <plat/mv_cesa.h> > > I think that plat/mv_cesa.h comes from the linux kernel. > > Cheers, > Davidm > > > -----Original Message----- > > From: added by portage for apache > > [mailto:ap...@at...] On Behalf Of md...@as... > > Sent: Monday, August 02, 2010 4:59 PM > > To: Flaig, Patrick > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi > > Ignore the warnings > > make sure that the following file exists and you include it: > > plat/mv_cesa.h > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > >> No such file >>or directory > > Regards > > Mihalis > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > Hello, > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > Here is the output of the build process: > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > mvAesBoxes.dat: No such file or directory > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > identifier is reported only once > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > function it appears in.) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > (first use in this function) > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > such file or directory > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > of function 'crypto_copy_bits_back' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > from incompatible pointer type > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > Any help or support is welcome :) > > > > > > Thanks and regards. > > > > > > Patrick > > > > > > > > > > > > > -------------------------------------------------------------------- > > ---------- The Palm PDK Hot Apps Program offers developers who use > > the Plug-In Development Kit to bring their C/C++ apps to Palm for a > > share of $1 Million in cash or HP Products. Visit us here for more > > details: > > http://p.sf.net/sfu/dev2dev-palm > > _______________________________________________ > > Ocf-linux-users mailing list > > Ocf...@li... > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-03 15:42:11
Attachments:
ocf_kirkwood_feroceon.tar.bz2
|
Hi David, As said the OCF driver for Kirkwood is now compiling. But I still have some issues when porting the driver for Feroceon. I've attached my modified drivers; maybe you can take a look into it and resolve the one or other dependency. I think you are more familiar with the Kirkwood driver and it should be easier for you to get the Feroceon driver compiling. Thanks a lot and best regards. Patrick -----Original Message----- From: Flaig, Patrick Sent: Tuesday, August 03, 2010 2:30 PM To: 'David McCullough' Cc: ocf...@li... Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Hi David, Thanks, for the files, now I'm able to compile the driver. When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. One comment from me, I think in the current release mvAesBoxes.dat is also missing. Is there a next release planned with fixes for the issues we found? Patrick -----Original Message----- From: David McCullough [mailto:dav...@mc...] Sent: Tuesday, August 03, 2010 11:39 AM To: Flaig, Patrick Cc: ocf...@li... Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Jivin Flaig, Patrick lays it down ... > Hi, > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > So I think I have to fix this first to continue with porting the driver. A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. Also a patch the was not in the last release which will fix the copyback errors you were seeing. Cheers, Davidm > -----Urspr??ngliche Nachricht----- > Von: David McCullough [mailto:dav...@mc...] > Gesendet: Dienstag, 3. August 2010 02:58 > An: Flaig, Patrick > Cc: ocf...@li... > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi, > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> > > and <plat/mv_cesa.h> > > I think that plat/mv_cesa.h comes from the linux kernel. > > Cheers, > Davidm > > > -----Original Message----- > > From: added by portage for apache > > [mailto:ap...@at...] On Behalf Of md...@as... > > Sent: Monday, August 02, 2010 4:59 PM > > To: Flaig, Patrick > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi > > Ignore the warnings > > make sure that the following file exists and you include it: > > plat/mv_cesa.h > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > >> No such file >>or directory > > Regards > > Mihalis > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > Hello, > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > Here is the output of the build process: > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > mvAesBoxes.dat: No such file or directory > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > identifier is reported only once > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > function it appears in.) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > (first use in this function) > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > such file or directory > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > of function 'crypto_copy_bits_back' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > from incompatible pointer type > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > Any help or support is welcome :) > > > > > > Thanks and regards. > > > > > > Patrick > > > > > > > > > > > > > -------------------------------------------------------------------- > > ---------- The Palm PDK Hot Apps Program offers developers who use > > the Plug-In Development Kit to bring their C/C++ apps to Palm for a > > share of $1 Million in cash or HP Products. Visit us here for more > > details: > > http://p.sf.net/sfu/dev2dev-palm > > _______________________________________________ > > Ocf-linux-users mailing list > > Ocf...@li... > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-09 07:18:28
|
Hi David, Did you already have the chance to look into the driver for the Feroceon? Patrick -----Original Message----- From: Flaig, Patrick Sent: Tuesday, August 03, 2010 5:41 PM To: 'David McCullough' Cc: 'ocf...@li...' Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Hi David, As said the OCF driver for Kirkwood is now compiling. But I still have some issues when porting the driver for Feroceon. I've attached my modified drivers; maybe you can take a look into it and resolve the one or other dependency. I think you are more familiar with the Kirkwood driver and it should be easier for you to get the Feroceon driver compiling. Thanks a lot and best regards. Patrick -----Original Message----- From: Flaig, Patrick Sent: Tuesday, August 03, 2010 2:30 PM To: 'David McCullough' Cc: ocf...@li... Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Hi David, Thanks, for the files, now I'm able to compile the driver. When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. One comment from me, I think in the current release mvAesBoxes.dat is also missing. Is there a next release planned with fixes for the issues we found? Patrick -----Original Message----- From: David McCullough [mailto:dav...@mc...] Sent: Tuesday, August 03, 2010 11:39 AM To: Flaig, Patrick Cc: ocf...@li... Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Jivin Flaig, Patrick lays it down ... > Hi, > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > So I think I have to fix this first to continue with porting the driver. A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. Also a patch the was not in the last release which will fix the copyback errors you were seeing. Cheers, Davidm > -----Urspr??ngliche Nachricht----- > Von: David McCullough [mailto:dav...@mc...] > Gesendet: Dienstag, 3. August 2010 02:58 > An: Flaig, Patrick > Cc: ocf...@li... > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi, > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> > > and <plat/mv_cesa.h> > > I think that plat/mv_cesa.h comes from the linux kernel. > > Cheers, > Davidm > > > -----Original Message----- > > From: added by portage for apache > > [mailto:ap...@at...] On Behalf Of md...@as... > > Sent: Monday, August 02, 2010 4:59 PM > > To: Flaig, Patrick > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi > > Ignore the warnings > > make sure that the following file exists and you include it: > > plat/mv_cesa.h > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > >> No such file >>or directory > > Regards > > Mihalis > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > Hello, > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > Here is the output of the build process: > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > mvAesBoxes.dat: No such file or directory > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > identifier is reported only once > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > function it appears in.) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > undeclared (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > (first use in this function) > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > (first use in this function) > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > CHK include/linux/version.h > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > CHK include/linux/utsrelease.h > > > SYMLINK include/asm -> include/asm-arm > > > CALL scripts/checksyscalls.sh > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > implemented > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > CHK include/linux/compile.h > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > such file or directory > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > of function 'crypto_copy_bits_back' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > pointer to incomplete type > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > from incompatible pointer type > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > make[1]: *** [crypto/ocf] Error 2 > > > make: *** [crypto] Error 2 > > > > > > Any help or support is welcome :) > > > > > > Thanks and regards. > > > > > > Patrick > > > > > > > > > > > > > -------------------------------------------------------------------- > > ---------- The Palm PDK Hot Apps Program offers developers who use > > the Plug-In Development Kit to bring their C/C++ apps to Palm for a > > share of $1 Million in cash or HP Products. Visit us here for more > > details: > > http://p.sf.net/sfu/dev2dev-palm > > _______________________________________________ > > Ocf-linux-users mailing list > > Ocf...@li... > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: David M. <dav...@mc...> - 2010-08-10 03:32:48
|
Jivin Flaig, Patrick lays it down ... > Hi David, > > Did you already have the chance to look into the driver for the Feroceon? Sorry, I'm a little busy just now, I intend to look at it for you soon, hopefully later in the week. Sorry, I meant to let you know :-( Cheers, Davidm > > Patrick > > -----Original Message----- > From: Flaig, Patrick > Sent: Tuesday, August 03, 2010 5:41 PM > To: 'David McCullough' > Cc: 'ocf...@li...' > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > Hi David, > > As said the OCF driver for Kirkwood is now compiling. But I still have some issues when porting the driver for Feroceon. > > I've attached my modified drivers; maybe you can take a look into it and resolve the one or other dependency. > I think you are more familiar with the Kirkwood driver and it should be easier for you to get the Feroceon driver compiling. > > Thanks a lot and best regards. > > Patrick > > -----Original Message----- > From: Flaig, Patrick > Sent: Tuesday, August 03, 2010 2:30 PM > To: 'David McCullough' > Cc: ocf...@li... > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > Hi David, > > Thanks, for the files, now I'm able to compile the driver. > When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. > > One comment from me, I think in the current release mvAesBoxes.dat is also missing. > > Is there a next release planned with fixes for the issues we found? > > Patrick > > -----Original Message----- > From: David McCullough [mailto:dav...@mc...] > Sent: Tuesday, August 03, 2010 11:39 AM > To: Flaig, Patrick > Cc: ocf...@li... > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi, > > > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > > So I think I have to fix this first to continue with porting the driver. > > A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. > > Also a patch the was not in the last release which will fix the copyback errors you were seeing. > > Cheers, > Davidm > > > > > -----Urspr??ngliche Nachricht----- > > Von: David McCullough [mailto:dav...@mc...] > > Gesendet: Dienstag, 3. August 2010 02:58 > > An: Flaig, Patrick > > Cc: ocf...@li... > > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > > > Jivin Flaig, Patrick lays it down ... > > > Hi, > > > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> > > > and <plat/mv_cesa.h> > > > > I think that plat/mv_cesa.h comes from the linux kernel. > > > > Cheers, > > Davidm > > > > > -----Original Message----- > > > From: added by portage for apache > > > [mailto:ap...@at...] On Behalf Of md...@as... > > > Sent: Monday, August 02, 2010 4:59 PM > > > To: Flaig, Patrick > > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > > (88F6xxx) Processors > > > > > > Hi > > > Ignore the warnings > > > make sure that the following file exists and you include it: > > > plat/mv_cesa.h > > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > > >> No such file >>or directory > > > Regards > > > Mihalis > > > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > > > Hello, > > > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > > > Here is the output of the build process: > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > > CHK include/linux/version.h > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > CHK include/linux/utsrelease.h > > > > SYMLINK include/asm -> include/asm-arm > > > > CALL scripts/checksyscalls.sh > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > implemented > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > CHK include/linux/compile.h > > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > > mvAesBoxes.dat: No such file or directory > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > > identifier is reported only once > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > > function it appears in.) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > > (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > > (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > > (first use in this function) > > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > make[1]: *** [crypto/ocf] Error 2 > > > > make: *** [crypto] Error 2 > > > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > CHK include/linux/version.h > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > CHK include/linux/utsrelease.h > > > > SYMLINK include/asm -> include/asm-arm > > > > CALL scripts/checksyscalls.sh > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > implemented > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not implemented > > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > CHK include/linux/compile.h > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > > such file or directory > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > > of function 'crypto_copy_bits_back' > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > > pointer to incomplete type > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > > pointer to incomplete type > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > > pointer to incomplete type > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > > from incompatible pointer type > > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > make[1]: *** [crypto/ocf] Error 2 > > > > make: *** [crypto] Error 2 > > > > > > > > Any help or support is welcome :) > > > > > > > > Thanks and regards. > > > > > > > > Patrick > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > ---------- The Palm PDK Hot Apps Program offers developers who use > > > the Plug-In Development Kit to bring their C/C++ apps to Palm for a > > > share of $1 Million in cash or HP Products. Visit us here for more > > > details: > > > http://p.sf.net/sfu/dev2dev-palm > > > _______________________________________________ > > > Ocf-linux-users mailing list > > > Ocf...@li... > > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > > > > > -- > > David McCullough, dav...@mc..., Ph:+61 734352815 > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-10 06:40:41
|
Thanks David, that would be great! Patrick -----Original Message----- From: David McCullough [mailto:dav...@mc...] Sent: Monday, August 09, 2010 1:36 PM To: Flaig, Patrick Cc: ocf...@li... Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Jivin Flaig, Patrick lays it down ... > Hi David, > > Did you already have the chance to look into the driver for the Feroceon? Sorry, I'm a little busy just now, I intend to look at it for you soon, hopefully later in the week. Sorry, I meant to let you know :-( Cheers, Davidm > > Patrick > > -----Original Message----- > From: Flaig, Patrick > Sent: Tuesday, August 03, 2010 5:41 PM > To: 'David McCullough' > Cc: 'ocf...@li...' > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > Hi David, > > As said the OCF driver for Kirkwood is now compiling. But I still have some issues when porting the driver for Feroceon. > > I've attached my modified drivers; maybe you can take a look into it and resolve the one or other dependency. > I think you are more familiar with the Kirkwood driver and it should be easier for you to get the Feroceon driver compiling. > > Thanks a lot and best regards. > > Patrick > > -----Original Message----- > From: Flaig, Patrick > Sent: Tuesday, August 03, 2010 2:30 PM > To: 'David McCullough' > Cc: ocf...@li... > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > Hi David, > > Thanks, for the files, now I'm able to compile the driver. > When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. > > One comment from me, I think in the current release mvAesBoxes.dat is also missing. > > Is there a next release planned with fixes for the issues we found? > > Patrick > > -----Original Message----- > From: David McCullough [mailto:dav...@mc...] > Sent: Tuesday, August 03, 2010 11:39 AM > To: Flaig, Patrick > Cc: ocf...@li... > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi, > > > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > > So I think I have to fix this first to continue with porting the driver. > > A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. > > Also a patch the was not in the last release which will fix the copyback errors you were seeing. > > Cheers, > Davidm > > > > > -----Urspr??ngliche Nachricht----- > > Von: David McCullough [mailto:dav...@mc...] > > Gesendet: Dienstag, 3. August 2010 02:58 > > An: Flaig, Patrick > > Cc: ocf...@li... > > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > > > Jivin Flaig, Patrick lays it down ... > > > Hi, > > > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> > > > and <plat/mv_cesa.h> > > > > I think that plat/mv_cesa.h comes from the linux kernel. > > > > Cheers, > > Davidm > > > > > -----Original Message----- > > > From: added by portage for apache > > > [mailto:ap...@at...] On Behalf Of > > > md...@as... > > > Sent: Monday, August 02, 2010 4:59 PM > > > To: Flaig, Patrick > > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > > (88F6xxx) Processors > > > > > > Hi > > > Ignore the warnings > > > make sure that the following file exists and you include it: > > > plat/mv_cesa.h > > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > > >> No such file >>or directory > > > Regards > > > Mihalis > > > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > > > Hello, > > > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > > > Here is the output of the build process: > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > > CHK include/linux/version.h > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > CHK include/linux/utsrelease.h > > > > SYMLINK include/asm -> include/asm-arm > > > > CALL scripts/checksyscalls.sh > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > implemented > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not > > > > implemented > > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > CHK include/linux/compile.h > > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > > mvAesBoxes.dat: No such file or directory > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > > identifier is reported only once > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > > function it appears in.) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > > (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > > undeclared (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > > (first use in this function) > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > > (first use in this function) > > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > make[1]: *** [crypto/ocf] Error 2 > > > > make: *** [crypto] Error 2 > > > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > CHK include/linux/version.h > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > CHK include/linux/utsrelease.h > > > > SYMLINK include/asm -> include/asm-arm > > > > CALL scripts/checksyscalls.sh > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > implemented > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not > > > > implemented > > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > CHK include/linux/compile.h > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > > such file or directory > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > > of function 'crypto_copy_bits_back' > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > > pointer to incomplete type > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > > pointer to incomplete type > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > > pointer to incomplete type > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > > from incompatible pointer type > > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > make[1]: *** [crypto/ocf] Error 2 > > > > make: *** [crypto] Error 2 > > > > > > > > Any help or support is welcome :) > > > > > > > > Thanks and regards. > > > > > > > > Patrick > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > -- > > > ---------- The Palm PDK Hot Apps Program offers developers who use > > > the Plug-In Development Kit to bring their C/C++ apps to Palm for > > > a share of $1 Million in cash or HP Products. Visit us here for > > > more > > > details: > > > http://p.sf.net/sfu/dev2dev-palm > > > _______________________________________________ > > > Ocf-linux-users mailing list > > > Ocf...@li... > > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > > > > > -- > > David McCullough, dav...@mc..., Ph:+61 734352815 > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: David M. <dav...@mc...> - 2010-08-11 07:03:07
|
Jivin Flaig, Patrick lays it down ... > Thanks David, > > that would be great! Try adding the following two lines to your Makefile and see how you go: mv_cesa-y += mvHal/mv_hal/ddr2/spd/mvSpd.o mvHal/mv78xx0_family/device/mvDevice.o mv_cesa-y += mvHal/mv_hal/eth-phy/mvEthPhy.o mvHal/mv_hal/cntmr/mvCntmr.o Cheers, Davidm > Patrick > -----Original Message----- > From: David McCullough [mailto:dav...@mc...] > Sent: Monday, August 09, 2010 1:36 PM > To: Flaig, Patrick > Cc: ocf...@li... > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi David, > > > > Did you already have the chance to look into the driver for the Feroceon? > > Sorry, I'm a little busy just now, I intend to look at it for you soon, hopefully later in the week. > > Sorry, I meant to let you know :-( > > Cheers, > Davidm > > > > > Patrick > > > > -----Original Message----- > > From: Flaig, Patrick > > Sent: Tuesday, August 03, 2010 5:41 PM > > To: 'David McCullough' > > Cc: 'ocf...@li...' > > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi David, > > > > As said the OCF driver for Kirkwood is now compiling. But I still have some issues when porting the driver for Feroceon. > > > > I've attached my modified drivers; maybe you can take a look into it and resolve the one or other dependency. > > I think you are more familiar with the Kirkwood driver and it should be easier for you to get the Feroceon driver compiling. > > > > Thanks a lot and best regards. > > > > Patrick > > > > -----Original Message----- > > From: Flaig, Patrick > > Sent: Tuesday, August 03, 2010 2:30 PM > > To: 'David McCullough' > > Cc: ocf...@li... > > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi David, > > > > Thanks, for the files, now I'm able to compile the driver. > > When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. > > > > One comment from me, I think in the current release mvAesBoxes.dat is also missing. > > > > Is there a next release planned with fixes for the issues we found? > > > > Patrick > > > > -----Original Message----- > > From: David McCullough [mailto:dav...@mc...] > > Sent: Tuesday, August 03, 2010 11:39 AM > > To: Flaig, Patrick > > Cc: ocf...@li... > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > > > Jivin Flaig, Patrick lays it down ... > > > Hi, > > > > > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > > > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > > > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > > > > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > > > So I think I have to fix this first to continue with porting the driver. > > > > A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. > > > > Also a patch the was not in the last release which will fix the copyback errors you were seeing. > > > > Cheers, > > Davidm > > > > > > > > > -----Urspr??ngliche Nachricht----- > > > Von: David McCullough [mailto:dav...@mc...] > > > Gesendet: Dienstag, 3. August 2010 02:58 > > > An: Flaig, Patrick > > > Cc: ocf...@li... > > > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > > (88F6xxx) Processors > > > > > > > > > Jivin Flaig, Patrick lays it down ... > > > > Hi, > > > > > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > > > > > But when it is the same, why is it included twice <cesa/mv_cesa.h> > > > > and <plat/mv_cesa.h> > > > > > > I think that plat/mv_cesa.h comes from the linux kernel. > > > > > > Cheers, > > > Davidm > > > > > > > -----Original Message----- > > > > From: added by portage for apache > > > > [mailto:ap...@at...] On Behalf Of > > > > md...@as... > > > > Sent: Monday, August 02, 2010 4:59 PM > > > > To: Flaig, Patrick > > > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > > > (88F6xxx) Processors > > > > > > > > Hi > > > > Ignore the warnings > > > > make sure that the following file exists and you include it: > > > > plat/mv_cesa.h > > > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > > > >> No such file >>or directory > > > > Regards > > > > Mihalis > > > > > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > > > > > Hello, > > > > > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > > > > > Here is the output of the build process: > > > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > > > CHK include/linux/version.h > > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > > CHK include/linux/utsrelease.h > > > > > SYMLINK include/asm -> include/asm-arm > > > > > CALL scripts/checksyscalls.sh > > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > > implemented > > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not > > > > > implemented > > > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > > CHK include/linux/compile.h > > > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > > > mvAesBoxes.dat: No such file or directory > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > > > identifier is reported only once > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > > > function it appears in.) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > > > (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > > > (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > > > (first use in this function) > > > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > > make[1]: *** [crypto/ocf] Error 2 > > > > > make: *** [crypto] Error 2 > > > > > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > > CHK include/linux/version.h > > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > > CHK include/linux/utsrelease.h > > > > > SYMLINK include/asm -> include/asm-arm > > > > > CALL scripts/checksyscalls.sh > > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > > implemented > > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not > > > > > implemented > > > > > <stdin>:1411:2: warning: #warning syscall ppoll not implemented > > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > > CHK include/linux/compile.h > > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > > > such file or directory > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > > > of function 'crypto_copy_bits_back' > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > > > pointer to incomplete type > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > > > pointer to incomplete type > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > > > pointer to incomplete type > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > > > from incompatible pointer type > > > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > > make[1]: *** [crypto/ocf] Error 2 > > > > > make: *** [crypto] Error 2 > > > > > > > > > > Any help or support is welcome :) > > > > > > > > > > Thanks and regards. > > > > > > > > > > Patrick > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > -- > > > > ---------- The Palm PDK Hot Apps Program offers developers who use > > > > the Plug-In Development Kit to bring their C/C++ apps to Palm for > > > > a share of $1 Million in cash or HP Products. Visit us here for > > > > more > > > > details: > > > > http://p.sf.net/sfu/dev2dev-palm > > > > _______________________________________________ > > > > Ocf-linux-users mailing list > > > > Ocf...@li... > > > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > > > > > > > > > -- > > > David McCullough, dav...@mc..., Ph:+61 734352815 > > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > > > > > > > > > -- > > David McCullough, dav...@mc..., Ph:+61 734352815 > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-11 16:07:30
|
Hi David, Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver. I've now compiled the OCF module and the driver directly into the kernel. I think I've now an understanding problem, how to configure OCF the right way. Do I have to configure the cryptographic API as well, with all the algorithms I want? How can I make sure that, if I have selected AES for example, the hardware acceleration is used? /proc/crypto is only showing module: kernel. Patrick -----Original Message----- From: David McCullough [mailto:dav...@mc...] Sent: Wednesday, August 11, 2010 9:03 AM To: Flaig, Patrick Cc: ocf...@li... Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors Jivin Flaig, Patrick lays it down ... > Thanks David, > > that would be great! Try adding the following two lines to your Makefile and see how you go: mv_cesa-y += mvHal/mv_hal/ddr2/spd/mvSpd.o mvHal/mv78xx0_family/device/mvDevice.o mv_cesa-y += mvHal/mv_hal/eth-phy/mvEthPhy.o mvHal/mv_hal/cntmr/mvCntmr.o Cheers, Davidm > Patrick > -----Original Message----- > From: David McCullough [mailto:dav...@mc...] > Sent: Monday, August 09, 2010 1:36 PM > To: Flaig, Patrick > Cc: ocf...@li... > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... > > Hi David, > > > > Did you already have the chance to look into the driver for the Feroceon? > > Sorry, I'm a little busy just now, I intend to look at it for you soon, hopefully later in the week. > > Sorry, I meant to let you know :-( > > Cheers, > Davidm > > > > > Patrick > > > > -----Original Message----- > > From: Flaig, Patrick > > Sent: Tuesday, August 03, 2010 5:41 PM > > To: 'David McCullough' > > Cc: 'ocf...@li...' > > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi David, > > > > As said the OCF driver for Kirkwood is now compiling. But I still have some issues when porting the driver for Feroceon. > > > > I've attached my modified drivers; maybe you can take a look into it and resolve the one or other dependency. > > I think you are more familiar with the Kirkwood driver and it should be easier for you to get the Feroceon driver compiling. > > > > Thanks a lot and best regards. > > > > Patrick > > > > -----Original Message----- > > From: Flaig, Patrick > > Sent: Tuesday, August 03, 2010 2:30 PM > > To: 'David McCullough' > > Cc: ocf...@li... > > Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > Hi David, > > > > Thanks, for the files, now I'm able to compile the driver. > > When I finished porting the driver for the feroceon platform I also can send you the code, for further use in the OCF project. > > > > One comment from me, I think in the current release mvAesBoxes.dat is also missing. > > > > Is there a next release planned with fixes for the issues we found? > > > > Patrick > > > > -----Original Message----- > > From: David McCullough [mailto:dav...@mc...] > > Sent: Tuesday, August 03, 2010 11:39 AM > > To: Flaig, Patrick > > Cc: ocf...@li... > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > (88F6xxx) Processors > > > > > > Jivin Flaig, Patrick lays it down ... > > > Hi, > > > > > > the mv_cesa.h is a Marvell specific file, which they use in their SDKs for the different processors. > > > I will now cross check my SDK if, there is an additional mv_cesa.h which I have to use. > > > My only problem is that I only have a SDK for the Feroceon not for the Kirkwood. > > > > > > Initially I only wanted to port the kirkwood driver to the feroceon platform, but then I saw that it is not possible to compile the kirkwood OCF driver. > > > So I think I have to fix this first to continue with porting the driver. > > > > A couple of things, attached is the mv_cesa.h from my kernel, not much in there really. > > > > Also a patch the was not in the last release which will fix the copyback errors you were seeing. > > > > Cheers, > > Davidm > > > > > > > > > -----Urspr??ngliche Nachricht----- > > > Von: David McCullough [mailto:dav...@mc...] > > > Gesendet: Dienstag, 3. August 2010 02:58 > > > An: Flaig, Patrick > > > Cc: ocf...@li... > > > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > > (88F6xxx) Processors > > > > > > > > > Jivin Flaig, Patrick lays it down ... > > > > Hi, > > > > > > > > Thanks for the hint, but where should this file or the directory "plat" be? > > > > Is mv_cesa.h the same as under crypto/ocf/Kirkwood/cesa? > > > > > > > > But when it is the same, why is it included twice > > > > <cesa/mv_cesa.h> and <plat/mv_cesa.h> > > > > > > I think that plat/mv_cesa.h comes from the linux kernel. > > > > > > Cheers, > > > Davidm > > > > > > > -----Original Message----- > > > > From: added by portage for apache > > > > [mailto:ap...@at...] On Behalf Of > > > > md...@as... > > > > Sent: Monday, August 02, 2010 4:59 PM > > > > To: Flaig, Patrick > > > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood > > > > (88F6xxx) Processors > > > > > > > > Hi > > > > Ignore the warnings > > > > make sure that the following file exists and you include it: > > > > plat/mv_cesa.h > > > > >> crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: > > > > >> No such file >>or directory > > > > Regards > > > > Mihalis > > > > > > > > Quoting "Flaig, Patrick" <Pat...@bd...>: > > > > > > > > > Hello, > > > > > > > > > > Maybe someone can help me; I'm getting some compile errors when > > > > > trying to compile the OCF driver for Marvell Kirkwood. > > > > > > > > > > I'm using a Kernel 2.6.31.14 with the latest OCF patches > > > > > (ocf-linux-26-20100325.patch) and the Marvell SDK 3.2 cross > > > > > compilers (arm-mv5vfp-linux-gnueabi). > > > > > > > > > > OCF without this driver enabled compiles without any problems. > > > > > > > > > > Here is the output of the build process: > > > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > > scripts/kconfig/conf -s arch/arm/Kconfig > > > > > CHK include/linux/version.h > > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > > CHK include/linux/utsrelease.h > > > > > SYMLINK include/asm -> include/asm-arm > > > > > CALL scripts/checksyscalls.sh > > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > > implemented > > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not > > > > > implemented > > > > > <stdin>:1411:2: warning: #warning syscall ppoll not > > > > > implemented > > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > > CHK include/linux/compile.h > > > > > CC crypto/ocf/kirkwood/cesa/mvCesa.o > > > > > CC crypto/ocf/kirkwood/cesa/mvLru.o > > > > > CC crypto/ocf/kirkwood/cesa/mvMD5.o > > > > > CC crypto/ocf/kirkwood/cesa/mvSHA1.o > > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:13:26: error: > > > > > mvAesBoxes.dat: No such file or directory > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'mul1': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'mask' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: (Each undeclared > > > > > identifier is reported only once > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: for each > > > > > function it appears in.) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Alogtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:29: error: 'Logtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'MixColumn': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'mask' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Alogtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:151: error: 'Logtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'InvMixColumn': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'mask' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Alogtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:169: error: 'Logtable' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelKeySched': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:221: error: 'S' undeclared > > > > > (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:222: error: 'rcon' > > > > > undeclared (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelEncrypt128': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:261: error: 'S' undeclared > > > > > (first use in this function) > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c: In function 'rijndaelDecrypt128': > > > > > crypto/ocf/kirkwood/cesa/AES/mvAesAlg.c:298: error: 'Si' undeclared > > > > > (first use in this function) > > > > > make[3]: *** [crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o] Error 1 > > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > > make[1]: *** [crypto/ocf] Error 2 > > > > > make: *** [crypto] Error 2 > > > > > > > > > > I was able to add the missing mvAesBoxes.dat(from the original > > > > > Marvell Kirkwood kernel), but still some compile errors. > > > > > > > > > > make ARCH=arm CROSS_COMPILE=arm-mv5vfp-linux-gnueabi- uImage > > > > > CHK include/linux/version.h > > > > > make[1]: `include/asm-arm/mach-types.h' is up to date. > > > > > CHK include/linux/utsrelease.h > > > > > SYMLINK include/asm -> include/asm-arm > > > > > CALL scripts/checksyscalls.sh > > > > > <stdin>:1351:2: warning: #warning syscall migrate_pages not > > > > > implemented > > > > > <stdin>:1407:2: warning: #warning syscall pselect6 not > > > > > implemented > > > > > <stdin>:1411:2: warning: #warning syscall ppoll not > > > > > implemented > > > > > <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented > > > > > CHK include/linux/compile.h > > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesAlg.o > > > > > CC crypto/ocf/kirkwood/cesa/AES/mvAesApi.o > > > > > CC crypto/ocf/kirkwood/cesa/mvCesaDebug.o > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugStatus': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:270: warning: format '%ld' > > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:278: warning: format '%ld' > > > > > expects type 'long int', but argument 4 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugQueue': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:306: warning: format '%ld' > > > > > expects type 'long int', but argument 5 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSramSA': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:358: warning: format '%ld' > > > > > expects type 'long int', but argument 3 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c: In function 'mvCesaDebugSram': > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:425: warning: format '%ld' > > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > > crypto/ocf/kirkwood/cesa/mvCesaDebug.c:434: warning: format '%ld' > > > > > expects type 'long int', but argument 2 has type 'unsigned int' > > > > > CC crypto/ocf/kirkwood/cesa_ocf_drv.o > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:49:26: error: plat/mv_cesa.h: No > > > > > such file or directory > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'cesa_ocf_process': > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:501: error: implicit declaration > > > > > of function 'crypto_copy_bits_back' > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'setup_tdma_mbus_windows': > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1115: error: dereferencing > > > > > pointer to incomplete type > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1116: error: dereferencing > > > > > pointer to incomplete type > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1117: error: dereferencing > > > > > pointer to incomplete type > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: In function 'mv_cesa_ocf_init': > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1201: warning: format '%x' > > > > > expects type 'unsigned int', but argument 4 has type 'void *' > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c: At top level: > > > > > crypto/ocf/kirkwood/cesa_ocf_drv.c:1271: warning: initialization > > > > > from incompatible pointer type > > > > > make[3]: *** [crypto/ocf/kirkwood/cesa_ocf_drv.o] Error 1 > > > > > make[2]: *** [crypto/ocf/kirkwood] Error 2 > > > > > make[1]: *** [crypto/ocf] Error 2 > > > > > make: *** [crypto] Error 2 > > > > > > > > > > Any help or support is welcome :) > > > > > > > > > > Thanks and regards. > > > > > > > > > > Patrick > > > > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------- > > > > -- > > > > -- > > > > ---------- The Palm PDK Hot Apps Program offers developers who > > > > use the Plug-In Development Kit to bring their C/C++ apps to > > > > Palm for a share of $1 Million in cash or HP Products. Visit us > > > > here for more > > > > details: > > > > http://p.sf.net/sfu/dev2dev-palm > > > > _______________________________________________ > > > > Ocf-linux-users mailing list > > > > Ocf...@li... > > > > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > > > > > > > > > > > > > > -- > > > David McCullough, dav...@mc..., Ph:+61 734352815 > > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > > > > > > > > > -- > > David McCullough, dav...@mc..., Ph:+61 734352815 > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > > > > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
|
From: Flaig, P. <Pat...@bd...> - 2010-08-16 14:14:39
|
Hi David,
I tried to do some measurements with the Feroceon driver and run into some problems.
It seems the hardware support is not fully working.
I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
---
/* Get crypto session for AES128 */
sess.cipher = CRYPTO_AES_CBC;
sess.keylen = KEY_SIZE;
sess.key = key;
if (ioctl(cfd, CIOCGSESSION, &sess)) {
perror("ioctl(CIOCGSESSION)");
return 1;
}
---
For me this looks like the driver is not loaded.
Did I forget to configure something?
How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
Thank you again for your answer(s).
Regards
Patrick
-----Original Message-----
From: Flaig, Patrick
Sent: Wednesday, August 11, 2010 6:07 PM
To: 'David McCullough'
Cc: ocf...@li...
Subject: RE: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
Hi David,
Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
I've now compiled the OCF module and the driver directly into the kernel.
I think I've now an understanding problem, how to configure OCF the right way.
Do I have to configure the cryptographic API as well, with all the algorithms I want?
How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
/proc/crypto is only showing module: kernel.
Patrick
|
|
From: David M. <dav...@mc...> - 2010-08-16 23:25:54
|
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
>
> I've now compiled the OCF module and the driver directly into the kernel.
>
> I think I've now an understanding problem, how to configure OCF the right way.
> Do I have to configure the cryptographic API as well, with all the algorithms I want?
> How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> /proc/crypto is only showing module: kernel.
OCF doesn't register with /proc/crypto as it is not part of the kernel
crypto.
If you only have one OCF driver loaded then only that option can be used.
OCF, by default, preferrs HW drivers over SW drivers. Of source this only
matters if you have more than one OCF crypto driver loaded, and one is SW.
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> I tried to do some measurements with the Feroceon driver and run into some problems.
> It seems the hardware support is not fully working.
>
> I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
>
> ---
> /* Get crypto session for AES128 */
> sess.cipher = CRYPTO_AES_CBC;
> sess.keylen = KEY_SIZE;
> sess.key = key;
> if (ioctl(cfd, CIOCGSESSION, &sess)) {
> perror("ioctl(CIOCGSESSION)");
> return 1;
> }
> ---
>
> For me this looks like the driver is not loaded.
> Did I forget to configure something?
This sounds like either the driver is not loaded and registered properly.
You said you have compiled everytihng into the kernel ? It might be easier
to use modules so you can debug it more easily (add trace etc).
Try turning on debug in the ocf and crypto drivers before you load your
driver.
echo 1 > /sys/module/ocf/parameters/crypto_debug
echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
Make sure your driver is registering with OCF for the alg's you want.
> How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
No, OCF has no fall back, it can only use the drivers that you have
loaded. If you want it to fall back to kernel SW versions you need to load
cryptosoft. OCF will use HW versions in preference to SW versions.
> Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
No. And while you are debugging your driver I recommend only loading one
driver (feroceon).
Get the cryptotest app that in bundled in with the OCF release and use that
to test your OCF driver. It can do everything you need to help debug the
driver and is very simple code that talks direct to OCF via /dev/crypto.
Cheers,
Davidm
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: Flaig, P. <Pat...@bd...> - 2010-08-17 06:59:08
|
Hi David,
Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details.
But how can I check if the hardware driver is used or loaded?
As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error.
---
/* Get crypto session for AES128 */
sess.cipher = CRYPTO_AES_CBC;
sess.keylen = KEY_SIZE;
sess.key = key;
if (ioctl(cfd, CIOCGSESSION, &sess)) {
perror("ioctl(CIOCGSESSION)");
return 1;
}
---
With the software driver no problem!
Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s.
If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working.
Is there a way to check if the hardware driver is working?
Patrick
-----Original Message-----
From: David McCullough [mailto:dav...@mc...]
Sent: Tuesday, August 17, 2010 1:24 AM
To: Flaig, Patrick
Cc: ocf...@li...
Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
>
> I've now compiled the OCF module and the driver directly into the kernel.
>
> I think I've now an understanding problem, how to configure OCF the right way.
> Do I have to configure the cryptographic API as well, with all the algorithms I want?
> How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> /proc/crypto is only showing module: kernel.
OCF doesn't register with /proc/crypto as it is not part of the kernel crypto.
If you only have one OCF driver loaded then only that option can be used.
OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW.
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> I tried to do some measurements with the Feroceon driver and run into some problems.
> It seems the hardware support is not fully working.
>
> I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
>
> ---
> /* Get crypto session for AES128 */
> sess.cipher = CRYPTO_AES_CBC;
> sess.keylen = KEY_SIZE;
> sess.key = key;
> if (ioctl(cfd, CIOCGSESSION, &sess)) {
> perror("ioctl(CIOCGSESSION)");
> return 1;
> }
> ---
>
> For me this looks like the driver is not loaded.
> Did I forget to configure something?
This sounds like either the driver is not loaded and registered properly.
You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc).
Try turning on debug in the ocf and crypto drivers before you load your driver.
echo 1 > /sys/module/ocf/parameters/crypto_debug
echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
Make sure your driver is registering with OCF for the alg's you want.
> How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions.
> Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
No. And while you are debugging your driver I recommend only loading one driver (feroceon).
Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto.
Cheers,
Davidm
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: David M. <dav...@mc...> - 2010-08-19 05:17:18
|
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details.
>
> But how can I check if the hardware driver is used or loaded?
>
> As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error.
> ---
> /* Get crypto session for AES128 */
> sess.cipher = CRYPTO_AES_CBC;
> sess.keylen = KEY_SIZE;
> sess.key = key;
> if (ioctl(cfd, CIOCGSESSION, &sess)) {
> perror("ioctl(CIOCGSESSION)");
> return 1;
> }
> ---
>
> With the software driver no problem!
>
> Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s.
> If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working.
> Is there a way to check if the hardware driver is working?
I did cover this in my previous email. Check below.
Turning on debug will let you know if the driver is active or not and tell
you lots more. Not debug while working means the driver is not being used.
Debug should also give you a detailed reason why EINVAL is being returned.
It will at least tell you the line/area the failure originated from.
The debug will come out on the console/system log or somewhere. Whereever
you kernel trace comes out.
Please try building and using the cryptotest program as well. I know you
have you own code, but the cryptotest program isa known quantity and I know
it does everything right ;-)
Cheers,
Davidm
> -----Original Message-----
> From: David McCullough [mailto:dav...@mc...]
> Sent: Tuesday, August 17, 2010 1:24 AM
> To: Flaig, Patrick
> Cc: ocf...@li...
> Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
>
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
> >
> > I've now compiled the OCF module and the driver directly into the kernel.
> >
> > I think I've now an understanding problem, how to configure OCF the right way.
> > Do I have to configure the cryptographic API as well, with all the algorithms I want?
> > How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> > /proc/crypto is only showing module: kernel.
>
> OCF doesn't register with /proc/crypto as it is not part of the kernel crypto.
>
> If you only have one OCF driver loaded then only that option can be used.
>
> OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW.
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > I tried to do some measurements with the Feroceon driver and run into some problems.
> > It seems the hardware support is not fully working.
> >
> > I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> > But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
> >
> > ---
> > /* Get crypto session for AES128 */
> > sess.cipher = CRYPTO_AES_CBC;
> > sess.keylen = KEY_SIZE;
> > sess.key = key;
> > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > perror("ioctl(CIOCGSESSION)");
> > return 1;
> > }
> > ---
> >
> > For me this looks like the driver is not loaded.
> > Did I forget to configure something?
>
> This sounds like either the driver is not loaded and registered properly.
> You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc).
>
> Try turning on debug in the ocf and crypto drivers before you load your driver.
>
> echo 1 > /sys/module/ocf/parameters/crypto_debug
> echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
>
> Make sure your driver is registering with OCF for the alg's you want.
>
> > How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
>
> No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions.
>
> > Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
>
> No. And while you are debugging your driver I recommend only loading one driver (feroceon).
>
> Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto.
>
> Cheers,
> Davidm
>
> --
> David McCullough, dav...@mc..., Ph:+61 734352815
> McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
>
>
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: Flaig, P. <Pat...@bd...> - 2010-08-20 13:03:29
|
Hi David,
I compiled the cryptotest for my target platform, and get the following response from the program when using
cryptosoft driver:
sh-3.2# ./cryptotest
cryptodev_open()
cryptodev_ioctl(cmd=c0046364 arg=be8979bc)
cryptodev_ioctl(CRIOGET)
cryptodev_ioctl(cmd=c030636a arg=be897a1c)
cryptodev_ioctl(CIOCGSESSION2)
cryptodev_ioctl(CIOCGSESSION2) - no mac
crypto/ocf/crypto.c,389: DRIVER_LOCK()
crypto/ocf/crypto.c,413: DRIVER_UNLOCK()
crypto/ocf/crypto.c,415: DRIVER_LOCK()
crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
csecreate()
cseadd()
cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
cryptodev_ioctl(CIOCCRYPT)
csefind()
cryptodev_op()
crypto_dispatch()
crypto/ocf/crypto.c,815: Q_LOCK()
crypto/ocf/crypto.c,839: Q_UNLOCK()
crypto_invoke()
crypto_done()
crypto/ocf/crypto.c,1156: Q_LOCK()
crypto/ocf/crypto.c,1158: Q_UNLOCK()
cryptodev_cb()
crypto/ocf/crypto.c,841: Q_LOCK()
crypto/ocf/crypto.c,867: Q_UNLOCK()
cryptodev_op about to WAIT
cryptodev_op finished WAITING error=0
cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
cryptodev_ioctl(CIOCCRYPT)
csefind()
cryptodev_op()
crypto_dispatch()
crypto/ocf/crypto.c,815: Q_LOCK()
crypto/ocf/crypto.c,839: Q_UNLOCK()
crypto_invoke()
crypto_done()
crypto/ocf/crypto.c,1156: Q_LOCK()
crypto/ocf/crypto.c,1158: Q_UNLOCK()
cryptodev_cb()
crypto/ocf/crypto.c,841: Q_LOCK()
crypto/ocf/crypto.c,867: Q_UNLOCK()
cryptodev_op about to WAIT
cryptodev_op finished WAITING error=0
cryptodev_ioctl(cmd=40046366 arg=be897a34)
cryptodev_ioctl(CIOCFSESSION)
csefind()
csedelete()
csefree()
crypto_freesession()
crypto/ocf/crypto.c,450: DRIVER_LOCK()
crypto/ocf/crypto.c,468: DRIVER_UNLOCK()
crypto/ocf/crypto.c,471: DRIVER_LOCK()
crypto/ocf/crypto.c,481: DRIVER_UNLOCK()
0.080 sec, cryptodev_release()
2 3des crypts, 8 bytes, 201 byte/sec, 0.0 Mb/sec
feroceon driver:
sh-3.2# ./cryptotest
cryptodev_open()
cryptodev_ioctl(cmd=c0046364 arg=bebe09bc)
cryptodev_ioctl(CRIOGET)
cryptodev_ioctl(cmd=c030636a arg=bebe0a1c)
cryptodev_ioctl(CIOCGSESSION2)
cryptodev_ioctl(CIOCGSESSION2) - no mac
crypto/ocf/crypto.c,389: DRIVER_LOCK()
crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
cryptodev_ioctl(CIOCGSESSION2) - newsession 22
cryptodev_ioctl(CIOCGSESSION2) - bail 22
cryptodev_release()
A similar output when using my program:
cryptodev_open()
cryptodev_ioctl(cmd=c0046364 arg=befa0cd0)
cryptodev_ioctl(CRIOGET)
cryptodev_ioctl(cmd=c01c6365 arg=befa0af8)
cryptodev_ioctl(CIOCGSESSION)
cryptodev_ioctl(CIOCGSESSION) - no mac
crypto/ocf/crypto.c,389: DRIVER_LOCK()
crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
cryptodev_ioctl(CIOCGSESSION) - newsession 22
cryptodev_ioctl(CIOCGSESSION) - bail 22
cryptodev_release()
Do you see any reason why the hardware driver is not working?
Regards
Patrick
-----Ursprüngliche Nachricht-----
Von: David McCullough [mailto:dav...@mc...]
Gesendet: Donnerstag, 19. August 2010 07:17
An: Flaig, Patrick
Cc: ocf...@li...
Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details.
>
> But how can I check if the hardware driver is used or loaded?
>
> As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error.
> ---
> /* Get crypto session for AES128 */
> sess.cipher = CRYPTO_AES_CBC;
> sess.keylen = KEY_SIZE;
> sess.key = key;
> if (ioctl(cfd, CIOCGSESSION, &sess)) {
> perror("ioctl(CIOCGSESSION)");
> return 1;
> }
> ---
>
> With the software driver no problem!
>
> Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s.
> If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working.
> Is there a way to check if the hardware driver is working?
I did cover this in my previous email. Check below.
Turning on debug will let you know if the driver is active or not and tell
you lots more. Not debug while working means the driver is not being used.
Debug should also give you a detailed reason why EINVAL is being returned.
It will at least tell you the line/area the failure originated from.
The debug will come out on the console/system log or somewhere. Whereever
you kernel trace comes out.
Please try building and using the cryptotest program as well. I know you
have you own code, but the cryptotest program isa known quantity and I know
it does everything right ;-)
Cheers,
Davidm
> -----Original Message-----
> From: David McCullough [mailto:dav...@mc...]
> Sent: Tuesday, August 17, 2010 1:24 AM
> To: Flaig, Patrick
> Cc: ocf...@li...
> Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
>
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
> >
> > I've now compiled the OCF module and the driver directly into the kernel.
> >
> > I think I've now an understanding problem, how to configure OCF the right way.
> > Do I have to configure the cryptographic API as well, with all the algorithms I want?
> > How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> > /proc/crypto is only showing module: kernel.
>
> OCF doesn't register with /proc/crypto as it is not part of the kernel crypto.
>
> If you only have one OCF driver loaded then only that option can be used.
>
> OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW.
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > I tried to do some measurements with the Feroceon driver and run into some problems.
> > It seems the hardware support is not fully working.
> >
> > I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> > But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
> >
> > ---
> > /* Get crypto session for AES128 */
> > sess.cipher = CRYPTO_AES_CBC;
> > sess.keylen = KEY_SIZE;
> > sess.key = key;
> > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > perror("ioctl(CIOCGSESSION)");
> > return 1;
> > }
> > ---
> >
> > For me this looks like the driver is not loaded.
> > Did I forget to configure something?
>
> This sounds like either the driver is not loaded and registered properly.
> You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc).
>
> Try turning on debug in the ocf and crypto drivers before you load your driver.
>
> echo 1 > /sys/module/ocf/parameters/crypto_debug
> echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
>
> Make sure your driver is registering with OCF for the alg's you want.
>
> > How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
>
> No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions.
>
> > Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
>
> No. And while you are debugging your driver I recommend only loading one driver (feroceon).
>
> Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto.
>
> Cheers,
> Davidm
>
> --
> David McCullough, dav...@mc..., Ph:+61 734352815
> McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
>
>
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: David M. <dav...@mc...> - 2010-08-23 03:36:10
|
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> I compiled the cryptotest for my target platform, and get the following response from the program when using
Looks like you driver isn't loading fully, it most certainly has registered
with OCF based on this output.
You will need to trace your drivers startup and check that it calls
crypto_register.
My guess is that it isn't,
Cheers,
Davidm
> cryptosoft driver:
>
> sh-3.2# ./cryptotest
> cryptodev_open()
> cryptodev_ioctl(cmd=c0046364 arg=be8979bc)
> cryptodev_ioctl(CRIOGET)
> cryptodev_ioctl(cmd=c030636a arg=be897a1c)
> cryptodev_ioctl(CIOCGSESSION2)
> cryptodev_ioctl(CIOCGSESSION2) - no mac
> crypto/ocf/crypto.c,389: DRIVER_LOCK()
> crypto/ocf/crypto.c,413: DRIVER_UNLOCK()
> crypto/ocf/crypto.c,415: DRIVER_LOCK()
> crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> csecreate()
> cseadd()
> cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
> cryptodev_ioctl(CIOCCRYPT)
> csefind()
> cryptodev_op()
> crypto_dispatch()
> crypto/ocf/crypto.c,815: Q_LOCK()
> crypto/ocf/crypto.c,839: Q_UNLOCK()
> crypto_invoke()
> crypto_done()
> crypto/ocf/crypto.c,1156: Q_LOCK()
> crypto/ocf/crypto.c,1158: Q_UNLOCK()
> cryptodev_cb()
> crypto/ocf/crypto.c,841: Q_LOCK()
> crypto/ocf/crypto.c,867: Q_UNLOCK()
> cryptodev_op about to WAIT
> cryptodev_op finished WAITING error=0
> cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
> cryptodev_ioctl(CIOCCRYPT)
> csefind()
> cryptodev_op()
> crypto_dispatch()
> crypto/ocf/crypto.c,815: Q_LOCK()
> crypto/ocf/crypto.c,839: Q_UNLOCK()
> crypto_invoke()
> crypto_done()
> crypto/ocf/crypto.c,1156: Q_LOCK()
> crypto/ocf/crypto.c,1158: Q_UNLOCK()
> cryptodev_cb()
> crypto/ocf/crypto.c,841: Q_LOCK()
> crypto/ocf/crypto.c,867: Q_UNLOCK()
> cryptodev_op about to WAIT
> cryptodev_op finished WAITING error=0
> cryptodev_ioctl(cmd=40046366 arg=be897a34)
> cryptodev_ioctl(CIOCFSESSION)
> csefind()
> csedelete()
> csefree()
> crypto_freesession()
> crypto/ocf/crypto.c,450: DRIVER_LOCK()
> crypto/ocf/crypto.c,468: DRIVER_UNLOCK()
> crypto/ocf/crypto.c,471: DRIVER_LOCK()
> crypto/ocf/crypto.c,481: DRIVER_UNLOCK()
> 0.080 sec, cryptodev_release()
> 2 3des crypts, 8 bytes, 201 byte/sec, 0.0 Mb/sec
>
>
> feroceon driver:
>
> sh-3.2# ./cryptotest
> cryptodev_open()
> cryptodev_ioctl(cmd=c0046364 arg=bebe09bc)
> cryptodev_ioctl(CRIOGET)
> cryptodev_ioctl(cmd=c030636a arg=bebe0a1c)
> cryptodev_ioctl(CIOCGSESSION2)
> cryptodev_ioctl(CIOCGSESSION2) - no mac
> crypto/ocf/crypto.c,389: DRIVER_LOCK()
> crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> cryptodev_ioctl(CIOCGSESSION2) - newsession 22
> cryptodev_ioctl(CIOCGSESSION2) - bail 22
> cryptodev_release()
>
> A similar output when using my program:
>
> cryptodev_open()
> cryptodev_ioctl(cmd=c0046364 arg=befa0cd0)
> cryptodev_ioctl(CRIOGET)
> cryptodev_ioctl(cmd=c01c6365 arg=befa0af8)
> cryptodev_ioctl(CIOCGSESSION)
> cryptodev_ioctl(CIOCGSESSION) - no mac
> crypto/ocf/crypto.c,389: DRIVER_LOCK()
> crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> cryptodev_ioctl(CIOCGSESSION) - newsession 22
> cryptodev_ioctl(CIOCGSESSION) - bail 22
> cryptodev_release()
>
>
> Do you see any reason why the hardware driver is not working?
>
> Regards
>
> Patrick
>
> -----Urspr??ngliche Nachricht-----
> Von: David McCullough [mailto:dav...@mc...]
> Gesendet: Donnerstag, 19. August 2010 07:17
> An: Flaig, Patrick
> Cc: ocf...@li...
> Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
>
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details.
> >
> > But how can I check if the hardware driver is used or loaded?
> >
> > As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error.
> > ---
> > /* Get crypto session for AES128 */
> > sess.cipher = CRYPTO_AES_CBC;
> > sess.keylen = KEY_SIZE;
> > sess.key = key;
> > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > perror("ioctl(CIOCGSESSION)");
> > return 1;
> > }
> > ---
> >
> > With the software driver no problem!
> >
> > Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s.
> > If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working.
> > Is there a way to check if the hardware driver is working?
>
> I did cover this in my previous email. Check below.
>
> Turning on debug will let you know if the driver is active or not and tell
> you lots more. Not debug while working means the driver is not being used.
>
> Debug should also give you a detailed reason why EINVAL is being returned.
> It will at least tell you the line/area the failure originated from.
>
> The debug will come out on the console/system log or somewhere. Whereever
> you kernel trace comes out.
>
> Please try building and using the cryptotest program as well. I know you
> have you own code, but the cryptotest program isa known quantity and I know
> it does everything right ;-)
>
> Cheers,
> Davidm
>
> > -----Original Message-----
> > From: David McCullough [mailto:dav...@mc...]
> > Sent: Tuesday, August 17, 2010 1:24 AM
> > To: Flaig, Patrick
> > Cc: ocf...@li...
> > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
> >
> >
> > Jivin Flaig, Patrick lays it down ...
> > > Hi David,
> > >
> > > Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
> > >
> > > I've now compiled the OCF module and the driver directly into the kernel.
> > >
> > > I think I've now an understanding problem, how to configure OCF the right way.
> > > Do I have to configure the cryptographic API as well, with all the algorithms I want?
> > > How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> > > /proc/crypto is only showing module: kernel.
> >
> > OCF doesn't register with /proc/crypto as it is not part of the kernel crypto.
> >
> > If you only have one OCF driver loaded then only that option can be used.
> >
> > OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW.
> >
> > Jivin Flaig, Patrick lays it down ...
> > > Hi David,
> > >
> > > I tried to do some measurements with the Feroceon driver and run into some problems.
> > > It seems the hardware support is not fully working.
> > >
> > > I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> > > But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
> > >
> > > ---
> > > /* Get crypto session for AES128 */
> > > sess.cipher = CRYPTO_AES_CBC;
> > > sess.keylen = KEY_SIZE;
> > > sess.key = key;
> > > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > > perror("ioctl(CIOCGSESSION)");
> > > return 1;
> > > }
> > > ---
> > >
> > > For me this looks like the driver is not loaded.
> > > Did I forget to configure something?
> >
> > This sounds like either the driver is not loaded and registered properly.
> > You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc).
> >
> > Try turning on debug in the ocf and crypto drivers before you load your driver.
> >
> > echo 1 > /sys/module/ocf/parameters/crypto_debug
> > echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
> >
> > Make sure your driver is registering with OCF for the alg's you want.
> >
> > > How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
> >
> > No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions.
> >
> > > Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
> >
> > No. And while you are debugging your driver I recommend only loading one driver (feroceon).
> >
> > Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto.
> >
> > Cheers,
> > Davidm
> >
> > --
> > David McCullough, dav...@mc..., Ph:+61 734352815
> > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
> >
> >
>
> --
> David McCullough, dav...@mc..., Ph:+61 734352815
> McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
>
>
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: Flaig, P. <Pat...@bd...> - 2010-08-24 16:15:58
|
Hello David,
I found the reason, why the driver is not working.
The complete device registration was missing for mach-mv78xx0.
I now tried to add that but still have some problems with a crashing driver.
To common.c I added
/*****************************************************************************
* Cryptographic Engines and Security Accelerator (CESA)
****************************************************************************/
static struct resource mv78xx0_crypto_resources[] = {
{
.name = "regs",
.start = CRYPTO_PHYS_BASE,
.end = CRYPTO_PHYS_BASE + 0xffff,
.flags = IORESOURCE_MEM,
}, {
.name = "sram",
.start = MV78XX0_SRAM_PHYS_BASE,
.end = MV78XX0_SRAM_PHYS_BASE + MV78XX0_SRAM_SIZE - 1,
.flags = IORESOURCE_MEM,
}, {
.name = "crypto interrupt",
.start = IRQ_MV78XX0_CRYPTO,
.end = IRQ_MV78XX0_CRYPTO,
.flags = IORESOURCE_IRQ,
},
};
static struct platform_device mv78xx0_crypto = {
.name = "mv_crypto",
.id = -1,
.num_resources = ARRAY_SIZE(mv78xx0_crypto_resources),
.resource = mv78xx0_crypto_resources,
};
void __init mv78xx0_crypto_init(void)
{
//kirkwood_clk_ctrl |= CGC_CRYPTO;
platform_device_register(&mv78xx0_crypto);
}
With the following settings (mv78xx0.h)
#define MV78XX0_SRAM_PHYS_BASE 0xf7000000
#define MV78XX0_SRAM_SIZE SZ_2K
#define CRYPTO_PHYS_BASE (MV78XX0_REGS_PHYS_BASE | 0x90000)
When loading the OCF driver for the feroceon it is crashing in setup_tdma_mbus_windows(...) in the following loop
for (i = 0; i < dev->plat_data->dram->num_cs; i++) {
struct mbus_dram_window *cs = dev->plat_data->dram->cs + i;
writel(
((cs->size - 1) & 0xffff0000) |
(cs->mbus_attr << 8) |
(dev->plat_data->dram->mbus_dram_target_id << 4) | 1,
dev->reg + WINDOW_CTRL(i)
);
writel(cs->base, dev->reg + WINDOW_BASE(i));
}
I think the SRAM configuration or something isn't set correct, but to get the correct values from the Feroceon documentation is not so easy.
So I tried to compare the values with the kirkwood.
The current dump from the kernel:
---
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = dec3c000
[00000000] *pgd=1fbd5031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1] PREEMPT
Modules linked in: mv_cesa(+) cryptodev(P) ocf(P)
CPU: 0 Tainted: P (2.6.31.14 #39)
PC is at mv_cesa_ocf_init+0x2a8/0x588 [mv_cesa]
LR is at mv_cesa_ocf_init+0x248/0x588 [mv_cesa]
pc : [<bf01aab4>] lr : [<bf01aa54>] psr: 40000013
sp : dec0fea8 ip : 00001e3e fp : be97ae24
r10: 00000000 r9 : dec0e000 r8 : bf032540
r7 : c04ba968 r6 : 00000000 r5 : 00000000 r4 : 00000000
r3 : 00000000 r2 : dec0fe9c r1 : bf0272cc r0 : 0000004f
Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 0005397f Table: 1ec3c000 DAC: 00000015
Process insmod (pid: 425, stack limit = 0xdec0e270)
Stack: (0xdec0fea8 to 0xdec10000)
fea0: 00000000 00000000 00000001 c04ba970 c04ba970 bf031f70
fec0: dfa3d0c0 c04d1d88 00000000 c0226b6c c04ba970 c0225c9c c04ba970 c04ba9a4
fee0: bf031f70 dfa3d0c0 c04d1d88 c0225db0 00000000 c0225d50 bf031f70 c02254c0
ff00: df8035b8 df81cb10 00000000 00000060 bf031f70 c0224dd0 bf0274a2 bf0274a2
ff20: dec0ff20 00000000 bf032340 bf031f70 00000000 c0026ae8 00000000 c0226084
ff40: 00000000 bf032340 bf035000 00000000 c0026ae8 bf03500c 00000000 c002631c
ff60: 00000000 bf032340 000c8082 401dd008 c0026ae8 00000000 bf032340 000c8082
ff80: 401dd008 c00733f0 401dd008 0028d614 000c8082 be97ae24 00000000 00000069
ffa0: 00000080 c0026940 be97ae24 00000000 401dd008 0028d614 000c8082 00000000
ffc0: be97ae24 00000000 00000069 00000080 00000001 00000002 be97ae28 be97ae24
ffe0: be97ae24 be97aaec 000225f0 40177ba4 60000010 401dd008 feedfeed feedfeed
[<bf01aab4>] (mv_cesa_ocf_init+0x2a8/0x588 [mv_cesa]) from [<c0226b6c>] (platform_drv_probe+0x14/0x18)
[<c0226b6c>] (platform_drv_probe+0x14/0x18) from [<c0225c9c>] (driver_probe_device+0xa8/0x15c)
[<c0225c9c>] (driver_probe_device+0xa8/0x15c) from [<c0225db0>] (__driver_attach+0x60/0x84)
[<c0225db0>] (__driver_attach+0x60/0x84) from [<c02254c0>] (bus_for_each_dev+0x44/0x74)
[<c02254c0>] (bus_for_each_dev+0x44/0x74) from [<c0224dd0>] (bus_add_driver+0x134/0x2bc)
[<c0224dd0>] (bus_add_driver+0x134/0x2bc) from [<c0226084>] (driver_register+0xa8/0x130)
[<c0226084>] (driver_register+0xa8/0x130) from [<bf03500c>] (mv_cesa_init+0xc/0x3c [mv_cesa])
[<bf03500c>] (mv_cesa_init+0xc/0x3c [mv_cesa]) from [<c002631c>] (do_one_initcall+0x5c/0x1bc)
[<c002631c>] (do_one_initcall+0x5c/0x1bc) from [<c00733f0>] (sys_init_module+0xb0/0x1c4)
[<c00733f0>] (sys_init_module+0xb0/0x1c4) from [<c0026940>] (ret_fast_syscall+0x0/0x2c)
Code: e590300c e7823001 e59f8224 e5983008 (e5932000)
---[ end trace dd976c01f3fc5834 ]---
Segmentation fault
---
Any ideas or hints for the right settings are welcome.
Thanks.
Patrick
-----Original Message-----
From: David McCullough [mailto:dav...@mc...]
Sent: Monday, August 23, 2010 4:54 AM
To: Flaig, Patrick
Cc: ocf...@li...
Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
Jivin Flaig, Patrick lays it down ...
> Hi David,
>
> I compiled the cryptotest for my target platform, and get the
> following response from the program when using
Looks like you driver isn't loading fully, it most certainly has registered with OCF based on this output.
You will need to trace your drivers startup and check that it calls crypto_register.
My guess is that it isn't,
Cheers,
Davidm
> cryptosoft driver:
>
> sh-3.2# ./cryptotest
> cryptodev_open()
> cryptodev_ioctl(cmd=c0046364 arg=be8979bc)
> cryptodev_ioctl(CRIOGET)
> cryptodev_ioctl(cmd=c030636a arg=be897a1c)
> cryptodev_ioctl(CIOCGSESSION2)
> cryptodev_ioctl(CIOCGSESSION2) - no mac
> crypto/ocf/crypto.c,389: DRIVER_LOCK()
> crypto/ocf/crypto.c,413: DRIVER_UNLOCK()
> crypto/ocf/crypto.c,415: DRIVER_LOCK()
> crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> csecreate()
> cseadd()
> cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
> cryptodev_ioctl(CIOCCRYPT)
> csefind()
> cryptodev_op()
> crypto_dispatch()
> crypto/ocf/crypto.c,815: Q_LOCK()
> crypto/ocf/crypto.c,839: Q_UNLOCK()
> crypto_invoke()
> crypto_done()
> crypto/ocf/crypto.c,1156: Q_LOCK()
> crypto/ocf/crypto.c,1158: Q_UNLOCK()
> cryptodev_cb()
> crypto/ocf/crypto.c,841: Q_LOCK()
> crypto/ocf/crypto.c,867: Q_UNLOCK()
> cryptodev_op about to WAIT
> cryptodev_op finished WAITING error=0
> cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
> cryptodev_ioctl(CIOCCRYPT)
> csefind()
> cryptodev_op()
> crypto_dispatch()
> crypto/ocf/crypto.c,815: Q_LOCK()
> crypto/ocf/crypto.c,839: Q_UNLOCK()
> crypto_invoke()
> crypto_done()
> crypto/ocf/crypto.c,1156: Q_LOCK()
> crypto/ocf/crypto.c,1158: Q_UNLOCK()
> cryptodev_cb()
> crypto/ocf/crypto.c,841: Q_LOCK()
> crypto/ocf/crypto.c,867: Q_UNLOCK()
> cryptodev_op about to WAIT
> cryptodev_op finished WAITING error=0
> cryptodev_ioctl(cmd=40046366 arg=be897a34)
> cryptodev_ioctl(CIOCFSESSION)
> csefind()
> csedelete()
> csefree()
> crypto_freesession()
> crypto/ocf/crypto.c,450: DRIVER_LOCK()
> crypto/ocf/crypto.c,468: DRIVER_UNLOCK()
> crypto/ocf/crypto.c,471: DRIVER_LOCK()
> crypto/ocf/crypto.c,481: DRIVER_UNLOCK()
> 0.080 sec, cryptodev_release()
> 2 3des crypts, 8 bytes, 201 byte/sec, 0.0 Mb/sec
>
>
> feroceon driver:
>
> sh-3.2# ./cryptotest
> cryptodev_open()
> cryptodev_ioctl(cmd=c0046364 arg=bebe09bc)
> cryptodev_ioctl(CRIOGET)
> cryptodev_ioctl(cmd=c030636a arg=bebe0a1c)
> cryptodev_ioctl(CIOCGSESSION2)
> cryptodev_ioctl(CIOCGSESSION2) - no mac
> crypto/ocf/crypto.c,389: DRIVER_LOCK()
> crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> cryptodev_ioctl(CIOCGSESSION2) - newsession 22
> cryptodev_ioctl(CIOCGSESSION2) - bail 22
> cryptodev_release()
>
> A similar output when using my program:
>
> cryptodev_open()
> cryptodev_ioctl(cmd=c0046364 arg=befa0cd0)
> cryptodev_ioctl(CRIOGET)
> cryptodev_ioctl(cmd=c01c6365 arg=befa0af8)
> cryptodev_ioctl(CIOCGSESSION)
> cryptodev_ioctl(CIOCGSESSION) - no mac
> crypto/ocf/crypto.c,389: DRIVER_LOCK()
> crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> cryptodev_ioctl(CIOCGSESSION) - newsession 22
> cryptodev_ioctl(CIOCGSESSION) - bail 22
> cryptodev_release()
>
>
> Do you see any reason why the hardware driver is not working?
>
> Regards
>
> Patrick
>
> -----Urspr??ngliche Nachricht-----
> Von: David McCullough [mailto:dav...@mc...]
> Gesendet: Donnerstag, 19. August 2010 07:17
> An: Flaig, Patrick
> Cc: ocf...@li...
> Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood
> (88F6xxx) Processors
>
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details.
> >
> > But how can I check if the hardware driver is used or loaded?
> >
> > As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error.
> > ---
> > /* Get crypto session for AES128 */
> > sess.cipher = CRYPTO_AES_CBC;
> > sess.keylen = KEY_SIZE;
> > sess.key = key;
> > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > perror("ioctl(CIOCGSESSION)");
> > return 1;
> > }
> > ---
> >
> > With the software driver no problem!
> >
> > Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s.
> > If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working.
> > Is there a way to check if the hardware driver is working?
>
> I did cover this in my previous email. Check below.
>
> Turning on debug will let you know if the driver is active or not and
> tell you lots more. Not debug while working means the driver is not being used.
>
> Debug should also give you a detailed reason why EINVAL is being returned.
> It will at least tell you the line/area the failure originated from.
>
> The debug will come out on the console/system log or somewhere.
> Whereever you kernel trace comes out.
>
> Please try building and using the cryptotest program as well. I know
> you have you own code, but the cryptotest program isa known quantity
> and I know it does everything right ;-)
>
> Cheers,
> Davidm
>
> > -----Original Message-----
> > From: David McCullough [mailto:dav...@mc...]
> > Sent: Tuesday, August 17, 2010 1:24 AM
> > To: Flaig, Patrick
> > Cc: ocf...@li...
> > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood
> > (88F6xxx) Processors
> >
> >
> > Jivin Flaig, Patrick lays it down ...
> > > Hi David,
> > >
> > > Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
> > >
> > > I've now compiled the OCF module and the driver directly into the kernel.
> > >
> > > I think I've now an understanding problem, how to configure OCF the right way.
> > > Do I have to configure the cryptographic API as well, with all the algorithms I want?
> > > How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> > > /proc/crypto is only showing module: kernel.
> >
> > OCF doesn't register with /proc/crypto as it is not part of the kernel crypto.
> >
> > If you only have one OCF driver loaded then only that option can be used.
> >
> > OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW.
> >
> > Jivin Flaig, Patrick lays it down ...
> > > Hi David,
> > >
> > > I tried to do some measurements with the Feroceon driver and run into some problems.
> > > It seems the hardware support is not fully working.
> > >
> > > I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> > > But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
> > >
> > > ---
> > > /* Get crypto session for AES128 */
> > > sess.cipher = CRYPTO_AES_CBC;
> > > sess.keylen = KEY_SIZE;
> > > sess.key = key;
> > > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > > perror("ioctl(CIOCGSESSION)");
> > > return 1;
> > > }
> > > ---
> > >
> > > For me this looks like the driver is not loaded.
> > > Did I forget to configure something?
> >
> > This sounds like either the driver is not loaded and registered properly.
> > You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc).
> >
> > Try turning on debug in the ocf and crypto drivers before you load your driver.
> >
> > echo 1 > /sys/module/ocf/parameters/crypto_debug
> > echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
> >
> > Make sure your driver is registering with OCF for the alg's you want.
> >
> > > How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
> >
> > No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions.
> >
> > > Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
> >
> > No. And while you are debugging your driver I recommend only loading one driver (feroceon).
> >
> > Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto.
> >
> > Cheers,
> > Davidm
> >
> > --
> > David McCullough, dav...@mc..., Ph:+61 734352815
> > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
> >
> >
>
> --
> David McCullough, dav...@mc..., Ph:+61 734352815
> McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
>
>
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: David M. <dav...@mc...> - 2010-08-25 05:25:11
|
Jivin Flaig, Patrick lays it down ...
> Hello David,
>
> I found the reason, why the driver is not working.
> The complete device registration was missing for mach-mv78xx0.
>
> I now tried to add that but still have some problems with a crashing driver.
>
> To common.c I added
>
> /*****************************************************************************
> * Cryptographic Engines and Security Accelerator (CESA)
> ****************************************************************************/
>
> static struct resource mv78xx0_crypto_resources[] = {
> {
> .name = "regs",
> .start = CRYPTO_PHYS_BASE,
> .end = CRYPTO_PHYS_BASE + 0xffff,
> .flags = IORESOURCE_MEM,
> }, {
> .name = "sram",
> .start = MV78XX0_SRAM_PHYS_BASE,
> .end = MV78XX0_SRAM_PHYS_BASE + MV78XX0_SRAM_SIZE - 1,
> .flags = IORESOURCE_MEM,
> }, {
> .name = "crypto interrupt",
> .start = IRQ_MV78XX0_CRYPTO,
> .end = IRQ_MV78XX0_CRYPTO,
> .flags = IORESOURCE_IRQ,
> },
> };
>
> static struct platform_device mv78xx0_crypto = {
> .name = "mv_crypto",
> .id = -1,
> .num_resources = ARRAY_SIZE(mv78xx0_crypto_resources),
> .resource = mv78xx0_crypto_resources,
> };
>
> void __init mv78xx0_crypto_init(void)
> {
> //kirkwood_clk_ctrl |= CGC_CRYPTO;
> platform_device_register(&mv78xx0_crypto);
> }
>
> With the following settings (mv78xx0.h)
>
> #define MV78XX0_SRAM_PHYS_BASE 0xf7000000
> #define MV78XX0_SRAM_SIZE SZ_2K
> #define CRYPTO_PHYS_BASE (MV78XX0_REGS_PHYS_BASE | 0x90000)
>
> When loading the OCF driver for the feroceon it is crashing in setup_tdma_mbus_windows(...) in the following loop
>
> for (i = 0; i < dev->plat_data->dram->num_cs; i++) {
> struct mbus_dram_window *cs = dev->plat_data->dram->cs + i;
> writel(
> ((cs->size - 1) & 0xffff0000) |
> (cs->mbus_attr << 8) |
> (dev->plat_data->dram->mbus_dram_target_id << 4) | 1,
> dev->reg + WINDOW_CTRL(i)
> );
> writel(cs->base, dev->reg + WINDOW_BASE(i));
> }
>
>
> I think the SRAM configuration or something isn't set correct, but to get the correct values from the Feroceon documentation is not so easy.
> So I tried to compare the values with the kirkwood.
>
> The current dump from the kernel:
> ---
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> pgd = dec3c000
> [00000000] *pgd=1fbd5031, *pte=00000000, *ppte=00000000
> Internal error: Oops: 17 [#1] PREEMPT
> Modules linked in: mv_cesa(+) cryptodev(P) ocf(P)
> CPU: 0 Tainted: P (2.6.31.14 #39)
> PC is at mv_cesa_ocf_init+0x2a8/0x588 [mv_cesa]
> LR is at mv_cesa_ocf_init+0x248/0x588 [mv_cesa]
> pc : [<bf01aab4>] lr : [<bf01aa54>] psr: 40000013
> sp : dec0fea8 ip : 00001e3e fp : be97ae24
> r10: 00000000 r9 : dec0e000 r8 : bf032540
> r7 : c04ba968 r6 : 00000000 r5 : 00000000 r4 : 00000000
> r3 : 00000000 r2 : dec0fe9c r1 : bf0272cc r0 : 0000004f
> Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
> Control: 0005397f Table: 1ec3c000 DAC: 00000015
> Process insmod (pid: 425, stack limit = 0xdec0e270)
> Stack: (0xdec0fea8 to 0xdec10000)
> fea0: 00000000 00000000 00000001 c04ba970 c04ba970 bf031f70
> fec0: dfa3d0c0 c04d1d88 00000000 c0226b6c c04ba970 c0225c9c c04ba970 c04ba9a4
> fee0: bf031f70 dfa3d0c0 c04d1d88 c0225db0 00000000 c0225d50 bf031f70 c02254c0
> ff00: df8035b8 df81cb10 00000000 00000060 bf031f70 c0224dd0 bf0274a2 bf0274a2
> ff20: dec0ff20 00000000 bf032340 bf031f70 00000000 c0026ae8 00000000 c0226084
> ff40: 00000000 bf032340 bf035000 00000000 c0026ae8 bf03500c 00000000 c002631c
> ff60: 00000000 bf032340 000c8082 401dd008 c0026ae8 00000000 bf032340 000c8082
> ff80: 401dd008 c00733f0 401dd008 0028d614 000c8082 be97ae24 00000000 00000069
> ffa0: 00000080 c0026940 be97ae24 00000000 401dd008 0028d614 000c8082 00000000
> ffc0: be97ae24 00000000 00000069 00000080 00000001 00000002 be97ae28 be97ae24
> ffe0: be97ae24 be97aaec 000225f0 40177ba4 60000010 401dd008 feedfeed feedfeed
> [<bf01aab4>] (mv_cesa_ocf_init+0x2a8/0x588 [mv_cesa]) from [<c0226b6c>] (platform_drv_probe+0x14/0x18)
> [<c0226b6c>] (platform_drv_probe+0x14/0x18) from [<c0225c9c>] (driver_probe_device+0xa8/0x15c)
> [<c0225c9c>] (driver_probe_device+0xa8/0x15c) from [<c0225db0>] (__driver_attach+0x60/0x84)
> [<c0225db0>] (__driver_attach+0x60/0x84) from [<c02254c0>] (bus_for_each_dev+0x44/0x74)
> [<c02254c0>] (bus_for_each_dev+0x44/0x74) from [<c0224dd0>] (bus_add_driver+0x134/0x2bc)
> [<c0224dd0>] (bus_add_driver+0x134/0x2bc) from [<c0226084>] (driver_register+0xa8/0x130)
> [<c0226084>] (driver_register+0xa8/0x130) from [<bf03500c>] (mv_cesa_init+0xc/0x3c [mv_cesa])
> [<bf03500c>] (mv_cesa_init+0xc/0x3c [mv_cesa]) from [<c002631c>] (do_one_initcall+0x5c/0x1bc)
> [<c002631c>] (do_one_initcall+0x5c/0x1bc) from [<c00733f0>] (sys_init_module+0xb0/0x1c4)
> [<c00733f0>] (sys_init_module+0xb0/0x1c4) from [<c0026940>] (ret_fast_syscall+0x0/0x2c)
> Code: e590300c e7823001 e59f8224 e5983008 (e5932000)
> ---[ end trace dd976c01f3fc5834 ]---
> Segmentation fault
> ---
>
> Any ideas or hints for the right settings are welcome.
Nothing from me really. I would be surprised if Marvel don't already have
support for this in their source tree. I would try there. They have been
pretty good OSS citizens and getting the code etc never seemed too hard.
I would also expect they have a working feroceon/ocf driver as well, could
be wrong though ;-)
Cheers,
Davidm
> -----Original Message-----
> From: David McCullough [mailto:dav...@mc...]
> Sent: Monday, August 23, 2010 4:54 AM
> To: Flaig, Patrick
> Cc: ocf...@li...
> Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors
>
>
> Jivin Flaig, Patrick lays it down ...
> > Hi David,
> >
> > I compiled the cryptotest for my target platform, and get the
> > following response from the program when using
>
> Looks like you driver isn't loading fully, it most certainly has registered with OCF based on this output.
>
> You will need to trace your drivers startup and check that it calls crypto_register.
>
> My guess is that it isn't,
>
> Cheers,
> Davidm
>
> > cryptosoft driver:
> >
> > sh-3.2# ./cryptotest
> > cryptodev_open()
> > cryptodev_ioctl(cmd=c0046364 arg=be8979bc)
> > cryptodev_ioctl(CRIOGET)
> > cryptodev_ioctl(cmd=c030636a arg=be897a1c)
> > cryptodev_ioctl(CIOCGSESSION2)
> > cryptodev_ioctl(CIOCGSESSION2) - no mac
> > crypto/ocf/crypto.c,389: DRIVER_LOCK()
> > crypto/ocf/crypto.c,413: DRIVER_UNLOCK()
> > crypto/ocf/crypto.c,415: DRIVER_LOCK()
> > crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> > csecreate()
> > cseadd()
> > cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
> > cryptodev_ioctl(CIOCCRYPT)
> > csefind()
> > cryptodev_op()
> > crypto_dispatch()
> > crypto/ocf/crypto.c,815: Q_LOCK()
> > crypto/ocf/crypto.c,839: Q_UNLOCK()
> > crypto_invoke()
> > crypto_done()
> > crypto/ocf/crypto.c,1156: Q_LOCK()
> > crypto/ocf/crypto.c,1158: Q_UNLOCK()
> > cryptodev_cb()
> > crypto/ocf/crypto.c,841: Q_LOCK()
> > crypto/ocf/crypto.c,867: Q_UNLOCK()
> > cryptodev_op about to WAIT
> > cryptodev_op finished WAITING error=0
> > cryptodev_ioctl(cmd=c01c6367 arg=be897a00)
> > cryptodev_ioctl(CIOCCRYPT)
> > csefind()
> > cryptodev_op()
> > crypto_dispatch()
> > crypto/ocf/crypto.c,815: Q_LOCK()
> > crypto/ocf/crypto.c,839: Q_UNLOCK()
> > crypto_invoke()
> > crypto_done()
> > crypto/ocf/crypto.c,1156: Q_LOCK()
> > crypto/ocf/crypto.c,1158: Q_UNLOCK()
> > cryptodev_cb()
> > crypto/ocf/crypto.c,841: Q_LOCK()
> > crypto/ocf/crypto.c,867: Q_UNLOCK()
> > cryptodev_op about to WAIT
> > cryptodev_op finished WAITING error=0
> > cryptodev_ioctl(cmd=40046366 arg=be897a34)
> > cryptodev_ioctl(CIOCFSESSION)
> > csefind()
> > csedelete()
> > csefree()
> > crypto_freesession()
> > crypto/ocf/crypto.c,450: DRIVER_LOCK()
> > crypto/ocf/crypto.c,468: DRIVER_UNLOCK()
> > crypto/ocf/crypto.c,471: DRIVER_LOCK()
> > crypto/ocf/crypto.c,481: DRIVER_UNLOCK()
> > 0.080 sec, cryptodev_release()
> > 2 3des crypts, 8 bytes, 201 byte/sec, 0.0 Mb/sec
> >
> >
> > feroceon driver:
> >
> > sh-3.2# ./cryptotest
> > cryptodev_open()
> > cryptodev_ioctl(cmd=c0046364 arg=bebe09bc)
> > cryptodev_ioctl(CRIOGET)
> > cryptodev_ioctl(cmd=c030636a arg=bebe0a1c)
> > cryptodev_ioctl(CIOCGSESSION2)
> > cryptodev_ioctl(CIOCGSESSION2) - no mac
> > crypto/ocf/crypto.c,389: DRIVER_LOCK()
> > crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> > cryptodev_ioctl(CIOCGSESSION2) - newsession 22
> > cryptodev_ioctl(CIOCGSESSION2) - bail 22
> > cryptodev_release()
> >
> > A similar output when using my program:
> >
> > cryptodev_open()
> > cryptodev_ioctl(cmd=c0046364 arg=befa0cd0)
> > cryptodev_ioctl(CRIOGET)
> > cryptodev_ioctl(cmd=c01c6365 arg=befa0af8)
> > cryptodev_ioctl(CIOCGSESSION)
> > cryptodev_ioctl(CIOCGSESSION) - no mac
> > crypto/ocf/crypto.c,389: DRIVER_LOCK()
> > crypto/ocf/crypto.c,425: DRIVER_UNLOCK()
> > cryptodev_ioctl(CIOCGSESSION) - newsession 22
> > cryptodev_ioctl(CIOCGSESSION) - bail 22
> > cryptodev_release()
> >
> >
> > Do you see any reason why the hardware driver is not working?
> >
> > Regards
> >
> > Patrick
> >
> > -----Urspr??ngliche Nachricht-----
> > Von: David McCullough [mailto:dav...@mc...]
> > Gesendet: Donnerstag, 19. August 2010 07:17
> > An: Flaig, Patrick
> > Cc: ocf...@li...
> > Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood
> > (88F6xxx) Processors
> >
> >
> > Jivin Flaig, Patrick lays it down ...
> > > Hi David,
> > >
> > > Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details.
> > >
> > > But how can I check if the hardware driver is used or loaded?
> > >
> > > As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error.
> > > ---
> > > /* Get crypto session for AES128 */
> > > sess.cipher = CRYPTO_AES_CBC;
> > > sess.keylen = KEY_SIZE;
> > > sess.key = key;
> > > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > > perror("ioctl(CIOCGSESSION)");
> > > return 1;
> > > }
> > > ---
> > >
> > > With the software driver no problem!
> > >
> > > Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s.
> > > If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working.
> > > Is there a way to check if the hardware driver is working?
> >
> > I did cover this in my previous email. Check below.
> >
> > Turning on debug will let you know if the driver is active or not and
> > tell you lots more. Not debug while working means the driver is not being used.
> >
> > Debug should also give you a detailed reason why EINVAL is being returned.
> > It will at least tell you the line/area the failure originated from.
> >
> > The debug will come out on the console/system log or somewhere.
> > Whereever you kernel trace comes out.
> >
> > Please try building and using the cryptotest program as well. I know
> > you have you own code, but the cryptotest program isa known quantity
> > and I know it does everything right ;-)
> >
> > Cheers,
> > Davidm
> >
> > > -----Original Message-----
> > > From: David McCullough [mailto:dav...@mc...]
> > > Sent: Tuesday, August 17, 2010 1:24 AM
> > > To: Flaig, Patrick
> > > Cc: ocf...@li...
> > > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood
> > > (88F6xxx) Processors
> > >
> > >
> > > Jivin Flaig, Patrick lays it down ...
> > > > Hi David,
> > > >
> > > > Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver.
> > > >
> > > > I've now compiled the OCF module and the driver directly into the kernel.
> > > >
> > > > I think I've now an understanding problem, how to configure OCF the right way.
> > > > Do I have to configure the cryptographic API as well, with all the algorithms I want?
> > > > How can I make sure that, if I have selected AES for example, the hardware acceleration is used?
> > > > /proc/crypto is only showing module: kernel.
> > >
> > > OCF doesn't register with /proc/crypto as it is not part of the kernel crypto.
> > >
> > > If you only have one OCF driver loaded then only that option can be used.
> > >
> > > OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW.
> > >
> > > Jivin Flaig, Patrick lays it down ...
> > > > Hi David,
> > > >
> > > > I tried to do some measurements with the Feroceon driver and run into some problems.
> > > > It seems the hardware support is not fully working.
> > > >
> > > > I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine.
> > > > But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error.
> > > >
> > > > ---
> > > > /* Get crypto session for AES128 */
> > > > sess.cipher = CRYPTO_AES_CBC;
> > > > sess.keylen = KEY_SIZE;
> > > > sess.key = key;
> > > > if (ioctl(cfd, CIOCGSESSION, &sess)) {
> > > > perror("ioctl(CIOCGSESSION)");
> > > > return 1;
> > > > }
> > > > ---
> > > >
> > > > For me this looks like the driver is not loaded.
> > > > Did I forget to configure something?
> > >
> > > This sounds like either the driver is not loaded and registered properly.
> > > You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc).
> > >
> > > Try turning on debug in the ocf and crypto drivers before you load your driver.
> > >
> > > echo 1 > /sys/module/ocf/parameters/crypto_debug
> > > echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug
> > >
> > > Make sure your driver is registering with OCF for the alg's you want.
> > >
> > > > How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm?
> > >
> > > No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions.
> > >
> > > > Do I have to enable the CRYPTOSOFT in combination with the hardware driver?
> > >
> > > No. And while you are debugging your driver I recommend only loading one driver (feroceon).
> > >
> > > Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto.
> > >
> > > Cheers,
> > > Davidm
> > >
> > > --
> > > David McCullough, dav...@mc..., Ph:+61 734352815
> > > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
> > >
> > >
> >
> > --
> > David McCullough, dav...@mc..., Ph:+61 734352815
> > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
> >
> >
>
> --
> David McCullough, dav...@mc..., Ph:+61 734352815
> McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
>
>
--
David McCullough, dav...@mc..., Ph:+61 734352815
McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org
|
|
From: Harro H. <hr...@gm...> - 2010-08-25 11:03:35
|
Hello Patrick, I had the same problem with kirkwood icw linux-2.6.33, the cause is that platform_data is missing. See ocf-add-platform_data-to-mv_crypto.patch in this thread: http://sourceforge.net/mailarchive/forum.php?thread_name=20100825052824.GB12893%40mcafee.com&forum_name=ocf-linux-users Regards, Harro On 24 August 2010 18:15, Flaig, Patrick <Pat...@bd...> wrote: > Hello David, > > I found the reason, why the driver is not working. > The complete device registration was missing for mach-mv78xx0. > > I now tried to add that but still have some problems with a crashing driver. > > To common.c I added > > /***************************************************************************** > * Cryptographic Engines and Security Accelerator (CESA) > ****************************************************************************/ > > static struct resource mv78xx0_crypto_resources[] = { > { > .name = "regs", > .start = CRYPTO_PHYS_BASE, > .end = CRYPTO_PHYS_BASE + 0xffff, > .flags = IORESOURCE_MEM, > }, { > .name = "sram", > .start = MV78XX0_SRAM_PHYS_BASE, > .end = MV78XX0_SRAM_PHYS_BASE + MV78XX0_SRAM_SIZE - 1, > .flags = IORESOURCE_MEM, > }, { > .name = "crypto interrupt", > .start = IRQ_MV78XX0_CRYPTO, > .end = IRQ_MV78XX0_CRYPTO, > .flags = IORESOURCE_IRQ, > }, > }; > > static struct platform_device mv78xx0_crypto = { > .name = "mv_crypto", > .id = -1, > .num_resources = ARRAY_SIZE(mv78xx0_crypto_resources), > .resource = mv78xx0_crypto_resources, > }; > > void __init mv78xx0_crypto_init(void) > { > //kirkwood_clk_ctrl |= CGC_CRYPTO; > platform_device_register(&mv78xx0_crypto); > } > > With the following settings (mv78xx0.h) > > #define MV78XX0_SRAM_PHYS_BASE 0xf7000000 > #define MV78XX0_SRAM_SIZE SZ_2K > #define CRYPTO_PHYS_BASE (MV78XX0_REGS_PHYS_BASE | 0x90000) > > When loading the OCF driver for the feroceon it is crashing in setup_tdma_mbus_windows(...) in the following loop > > for (i = 0; i < dev->plat_data->dram->num_cs; i++) { > struct mbus_dram_window *cs = dev->plat_data->dram->cs + i; > writel( > ((cs->size - 1) & 0xffff0000) | > (cs->mbus_attr << 8) | > (dev->plat_data->dram->mbus_dram_target_id << 4) | 1, > dev->reg + WINDOW_CTRL(i) > ); > writel(cs->base, dev->reg + WINDOW_BASE(i)); > } > > > I think the SRAM configuration or something isn't set correct, but to get the correct values from the Feroceon documentation is not so easy. > So I tried to compare the values with the kirkwood. > > The current dump from the kernel: > --- > Unable to handle kernel NULL pointer dereference at virtual address 00000000 > pgd = dec3c000 > [00000000] *pgd=1fbd5031, *pte=00000000, *ppte=00000000 > Internal error: Oops: 17 [#1] PREEMPT > Modules linked in: mv_cesa(+) cryptodev(P) ocf(P) > CPU: 0 Tainted: P (2.6.31.14 #39) > PC is at mv_cesa_ocf_init+0x2a8/0x588 [mv_cesa] > LR is at mv_cesa_ocf_init+0x248/0x588 [mv_cesa] > pc : [<bf01aab4>] lr : [<bf01aa54>] psr: 40000013 > sp : dec0fea8 ip : 00001e3e fp : be97ae24 > r10: 00000000 r9 : dec0e000 r8 : bf032540 > r7 : c04ba968 r6 : 00000000 r5 : 00000000 r4 : 00000000 > r3 : 00000000 r2 : dec0fe9c r1 : bf0272cc r0 : 0000004f > Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user > Control: 0005397f Table: 1ec3c000 DAC: 00000015 > Process insmod (pid: 425, stack limit = 0xdec0e270) > Stack: (0xdec0fea8 to 0xdec10000) > fea0: 00000000 00000000 00000001 c04ba970 c04ba970 bf031f70 > fec0: dfa3d0c0 c04d1d88 00000000 c0226b6c c04ba970 c0225c9c c04ba970 c04ba9a4 > fee0: bf031f70 dfa3d0c0 c04d1d88 c0225db0 00000000 c0225d50 bf031f70 c02254c0 > ff00: df8035b8 df81cb10 00000000 00000060 bf031f70 c0224dd0 bf0274a2 bf0274a2 > ff20: dec0ff20 00000000 bf032340 bf031f70 00000000 c0026ae8 00000000 c0226084 > ff40: 00000000 bf032340 bf035000 00000000 c0026ae8 bf03500c 00000000 c002631c > ff60: 00000000 bf032340 000c8082 401dd008 c0026ae8 00000000 bf032340 000c8082 > ff80: 401dd008 c00733f0 401dd008 0028d614 000c8082 be97ae24 00000000 00000069 > ffa0: 00000080 c0026940 be97ae24 00000000 401dd008 0028d614 000c8082 00000000 > ffc0: be97ae24 00000000 00000069 00000080 00000001 00000002 be97ae28 be97ae24 > ffe0: be97ae24 be97aaec 000225f0 40177ba4 60000010 401dd008 feedfeed feedfeed > [<bf01aab4>] (mv_cesa_ocf_init+0x2a8/0x588 [mv_cesa]) from [<c0226b6c>] (platform_drv_probe+0x14/0x18) > [<c0226b6c>] (platform_drv_probe+0x14/0x18) from [<c0225c9c>] (driver_probe_device+0xa8/0x15c) > [<c0225c9c>] (driver_probe_device+0xa8/0x15c) from [<c0225db0>] (__driver_attach+0x60/0x84) > [<c0225db0>] (__driver_attach+0x60/0x84) from [<c02254c0>] (bus_for_each_dev+0x44/0x74) > [<c02254c0>] (bus_for_each_dev+0x44/0x74) from [<c0224dd0>] (bus_add_driver+0x134/0x2bc) > [<c0224dd0>] (bus_add_driver+0x134/0x2bc) from [<c0226084>] (driver_register+0xa8/0x130) > [<c0226084>] (driver_register+0xa8/0x130) from [<bf03500c>] (mv_cesa_init+0xc/0x3c [mv_cesa]) > [<bf03500c>] (mv_cesa_init+0xc/0x3c [mv_cesa]) from [<c002631c>] (do_one_initcall+0x5c/0x1bc) > [<c002631c>] (do_one_initcall+0x5c/0x1bc) from [<c00733f0>] (sys_init_module+0xb0/0x1c4) > [<c00733f0>] (sys_init_module+0xb0/0x1c4) from [<c0026940>] (ret_fast_syscall+0x0/0x2c) > Code: e590300c e7823001 e59f8224 e5983008 (e5932000) > ---[ end trace dd976c01f3fc5834 ]--- > Segmentation fault > --- > > Any ideas or hints for the right settings are welcome. > > Thanks. > > Patrick > > -----Original Message----- > From: David McCullough [mailto:dav...@mc...] > Sent: Monday, August 23, 2010 4:54 AM > To: Flaig, Patrick > Cc: ocf...@li... > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood (88F6xxx) Processors > > > Jivin Flaig, Patrick lays it down ... >> Hi David, >> >> I compiled the cryptotest for my target platform, and get the >> following response from the program when using > > Looks like you driver isn't loading fully, it most certainly has registered with OCF based on this output. > > You will need to trace your drivers startup and check that it calls crypto_register. > > My guess is that it isn't, > > Cheers, > Davidm > >> cryptosoft driver: >> >> sh-3.2# ./cryptotest >> cryptodev_open() >> cryptodev_ioctl(cmd=c0046364 arg=be8979bc) >> cryptodev_ioctl(CRIOGET) >> cryptodev_ioctl(cmd=c030636a arg=be897a1c) >> cryptodev_ioctl(CIOCGSESSION2) >> cryptodev_ioctl(CIOCGSESSION2) - no mac >> crypto/ocf/crypto.c,389: DRIVER_LOCK() >> crypto/ocf/crypto.c,413: DRIVER_UNLOCK() >> crypto/ocf/crypto.c,415: DRIVER_LOCK() >> crypto/ocf/crypto.c,425: DRIVER_UNLOCK() >> csecreate() >> cseadd() >> cryptodev_ioctl(cmd=c01c6367 arg=be897a00) >> cryptodev_ioctl(CIOCCRYPT) >> csefind() >> cryptodev_op() >> crypto_dispatch() >> crypto/ocf/crypto.c,815: Q_LOCK() >> crypto/ocf/crypto.c,839: Q_UNLOCK() >> crypto_invoke() >> crypto_done() >> crypto/ocf/crypto.c,1156: Q_LOCK() >> crypto/ocf/crypto.c,1158: Q_UNLOCK() >> cryptodev_cb() >> crypto/ocf/crypto.c,841: Q_LOCK() >> crypto/ocf/crypto.c,867: Q_UNLOCK() >> cryptodev_op about to WAIT >> cryptodev_op finished WAITING error=0 >> cryptodev_ioctl(cmd=c01c6367 arg=be897a00) >> cryptodev_ioctl(CIOCCRYPT) >> csefind() >> cryptodev_op() >> crypto_dispatch() >> crypto/ocf/crypto.c,815: Q_LOCK() >> crypto/ocf/crypto.c,839: Q_UNLOCK() >> crypto_invoke() >> crypto_done() >> crypto/ocf/crypto.c,1156: Q_LOCK() >> crypto/ocf/crypto.c,1158: Q_UNLOCK() >> cryptodev_cb() >> crypto/ocf/crypto.c,841: Q_LOCK() >> crypto/ocf/crypto.c,867: Q_UNLOCK() >> cryptodev_op about to WAIT >> cryptodev_op finished WAITING error=0 >> cryptodev_ioctl(cmd=40046366 arg=be897a34) >> cryptodev_ioctl(CIOCFSESSION) >> csefind() >> csedelete() >> csefree() >> crypto_freesession() >> crypto/ocf/crypto.c,450: DRIVER_LOCK() >> crypto/ocf/crypto.c,468: DRIVER_UNLOCK() >> crypto/ocf/crypto.c,471: DRIVER_LOCK() >> crypto/ocf/crypto.c,481: DRIVER_UNLOCK() >> 0.080 sec, cryptodev_release() >> 2 3des crypts, 8 bytes, 201 byte/sec, 0.0 Mb/sec >> >> >> feroceon driver: >> >> sh-3.2# ./cryptotest >> cryptodev_open() >> cryptodev_ioctl(cmd=c0046364 arg=bebe09bc) >> cryptodev_ioctl(CRIOGET) >> cryptodev_ioctl(cmd=c030636a arg=bebe0a1c) >> cryptodev_ioctl(CIOCGSESSION2) >> cryptodev_ioctl(CIOCGSESSION2) - no mac >> crypto/ocf/crypto.c,389: DRIVER_LOCK() >> crypto/ocf/crypto.c,425: DRIVER_UNLOCK() >> cryptodev_ioctl(CIOCGSESSION2) - newsession 22 >> cryptodev_ioctl(CIOCGSESSION2) - bail 22 >> cryptodev_release() >> >> A similar output when using my program: >> >> cryptodev_open() >> cryptodev_ioctl(cmd=c0046364 arg=befa0cd0) >> cryptodev_ioctl(CRIOGET) >> cryptodev_ioctl(cmd=c01c6365 arg=befa0af8) >> cryptodev_ioctl(CIOCGSESSION) >> cryptodev_ioctl(CIOCGSESSION) - no mac >> crypto/ocf/crypto.c,389: DRIVER_LOCK() >> crypto/ocf/crypto.c,425: DRIVER_UNLOCK() >> cryptodev_ioctl(CIOCGSESSION) - newsession 22 >> cryptodev_ioctl(CIOCGSESSION) - bail 22 >> cryptodev_release() >> >> >> Do you see any reason why the hardware driver is not working? >> >> Regards >> >> Patrick >> >> -----Urspr??ngliche Nachricht----- >> Von: David McCullough [mailto:dav...@mc...] >> Gesendet: Donnerstag, 19. August 2010 07:17 >> An: Flaig, Patrick >> Cc: ocf...@li... >> Betreff: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood >> (88F6xxx) Processors >> >> >> Jivin Flaig, Patrick lays it down ... >> > Hi David, >> > >> > Thanks for the feedback, ok now I know that cannot reference "/proc/crypto" for OCF details. >> > >> > But how can I check if the hardware driver is used or loaded? >> > >> > As said when I try to use an AES CBC algorithm with the Feroceon driver I'm getting in invalid argument error. >> > --- >> > /* Get crypto session for AES128 */ >> > sess.cipher = CRYPTO_AES_CBC; >> > sess.keylen = KEY_SIZE; >> > sess.key = key; >> > if (ioctl(cfd, CIOCGSESSION, &sess)) { >> > perror("ioctl(CIOCGSESSION)"); >> > return 1; >> > } >> > --- >> > >> > With the software driver no problem! >> > >> > Some time ago I did some measurements with the original Marvell SDK Kernel for the Feroceon. Without HW driver I was able to encrypt about 9 MB/s, with HW support 36 MB/s. >> > If I now do the same measurements again with loaded SW and HW driver I'm only getting a rate about 9 MB/s, which leads to the speculation that only the software driver is working. >> > Is there a way to check if the hardware driver is working? >> >> I did cover this in my previous email. Check below. >> >> Turning on debug will let you know if the driver is active or not and >> tell you lots more. Not debug while working means the driver is not being used. >> >> Debug should also give you a detailed reason why EINVAL is being returned. >> It will at least tell you the line/area the failure originated from. >> >> The debug will come out on the console/system log or somewhere. >> Whereever you kernel trace comes out. >> >> Please try building and using the cryptotest program as well. I know >> you have you own code, but the cryptotest program isa known quantity >> and I know it does everything right ;-) >> >> Cheers, >> Davidm >> >> > -----Original Message----- >> > From: David McCullough [mailto:dav...@mc...] >> > Sent: Tuesday, August 17, 2010 1:24 AM >> > To: Flaig, Patrick >> > Cc: ocf...@li... >> > Subject: Re: [Ocf-linux-users] OCF driver for Marvell Kirkwood >> > (88F6xxx) Processors >> > >> > >> > Jivin Flaig, Patrick lays it down ... >> > > Hi David, >> > > >> > > Thanks a lot, the additional lines in the Makefile let me compile the Feroceon driver. >> > > >> > > I've now compiled the OCF module and the driver directly into the kernel. >> > > >> > > I think I've now an understanding problem, how to configure OCF the right way. >> > > Do I have to configure the cryptographic API as well, with all the algorithms I want? >> > > How can I make sure that, if I have selected AES for example, the hardware acceleration is used? >> > > /proc/crypto is only showing module: kernel. >> > >> > OCF doesn't register with /proc/crypto as it is not part of the kernel crypto. >> > >> > If you only have one OCF driver loaded then only that option can be used. >> > >> > OCF, by default, preferrs HW drivers over SW drivers. Of source this only matters if you have more than one OCF crypto driver loaded, and one is SW. >> > >> > Jivin Flaig, Patrick lays it down ... >> > > Hi David, >> > > >> > > I tried to do some measurements with the Feroceon driver and run into some problems. >> > > It seems the hardware support is not fully working. >> > > >> > > I configured OCF to use the CRYPTOSOFT driver and run a little test application, everything works fine. >> > > But when I disabled the CRYPTOSOFT driver and enabled the FEROCEON driver, my test failed with an "ioctl(CIOCGSESSION): Invalid argument" error. >> > > >> > > --- >> > > /* Get crypto session for AES128 */ >> > > sess.cipher = CRYPTO_AES_CBC; >> > > sess.keylen = KEY_SIZE; >> > > sess.key = key; >> > > if (ioctl(cfd, CIOCGSESSION, &sess)) { >> > > perror("ioctl(CIOCGSESSION)"); >> > > return 1; >> > > } >> > > --- >> > > >> > > For me this looks like the driver is not loaded. >> > > Did I forget to configure something? >> > >> > This sounds like either the driver is not loaded and registered properly. >> > You said you have compiled everytihng into the kernel ? It might be easier to use modules so you can debug it more easily (add trace etc). >> > >> > Try turning on debug in the ocf and crypto drivers before you load your driver. >> > >> > echo 1 > /sys/module/ocf/parameters/crypto_debug >> > echo 1 > /sys/module/cryptodev/parameters/cryptodev_debug >> > >> > Make sure your driver is registering with OCF for the alg's you want. >> > >> > > How will OCF handle algorithms that are not supported by the hardware, will the OCF switch to the kernel algorithm? >> > >> > No, OCF has no fall back, it can only use the drivers that you have loaded. If you want it to fall back to kernel SW versions you need to load cryptosoft. OCF will use HW versions in preference to SW versions. >> > >> > > Do I have to enable the CRYPTOSOFT in combination with the hardware driver? >> > >> > No. And while you are debugging your driver I recommend only loading one driver (feroceon). >> > >> > Get the cryptotest app that in bundled in with the OCF release and use that to test your OCF driver. It can do everything you need to help debug the driver and is very simple code that talks direct to OCF via /dev/crypto. >> > >> > Cheers, >> > Davidm >> > >> > -- >> > David McCullough, dav...@mc..., Ph:+61 734352815 >> > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org >> > >> > >> >> -- >> David McCullough, dav...@mc..., Ph:+61 734352815 >> McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org >> >> > > -- > David McCullough, dav...@mc..., Ph:+61 734352815 > McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org > > ------------------------------------------------------------------------------ > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > Be part of this innovative community and reach millions of netbook users > worldwide. Take advantage of special opportunities to increase revenue and > speed time-to-market. Join now, and jumpstart your future. > http://p.sf.net/sfu/intel-atom-d2d > _______________________________________________ > Ocf-linux-users mailing list > Ocf...@li... > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X