moved on to a kernel cmem problem

2009-04-12 Thread Mat Laibowitz
In order to debug my mpeg4dec app side program I was looking dmai to see how it accessed the viddec2 ce interface. Along the way I decided to try and compile it and also to try and upgrade some components. I modified the dmai source to support my custom board and can compile it. Now I am having

Re: moved on to a kernel cmem problem

2009-04-12 Thread Yusuf Caglar AKYUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mat Laibowitz wrote: In order to debug my mpeg4dec app side program I was looking dmai to see how it accessed the viddec2 ce interface. Along the way I decided to try and compile it and also to try and upgrade some components. I modified the

gcc error

2009-04-12 Thread amol bankhele
hi, i am amol from INDIA , while upgrading kernel after this command *make menuconfig get this following error* *HOSTCC scripts/basic/fixdep /bin/sh: gcc: command not found make[1]: *** [scripts/basic/fixdep] Error 127 make: *** [scripts_basic] Error 2 * *[r...@localhost linux-2.6.30-rc1]#

Re: moved on to a kernel cmem problem

2009-04-12 Thread Steve Chen
On Sun, 2009-04-12 at 10:08 +0300, Yusuf Caglar AKYUZ wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mat Laibowitz wrote: In order to debug my mpeg4dec app side program I was looking dmai to see how it accessed the viddec2 ce interface. Along the way I decided to try and

Re: gcc error

2009-04-12 Thread Steve Chen
On Sun, 2009-04-12 at 17:37 +0530, amol bankhele wrote: hi, i am amol from INDIA , while upgrading kernel after this command make menuconfig get this following error May want to do something like make ARCH=arm CROSS_COMPILE=arm_v5t_le- menuconfig and make sure your toolchain is in

Re: moved on to a kernel cmem problem

2009-04-12 Thread Mat Laibowitz
Thanks for the replies. I am using kernel 2.6.22 and dsplink 1.60. Maybe your findings could help even if these are different versions. From what you guys are saying, it seems that the app is looking for dsplink and not finding it? When you change the bootarg to mem=118M do you also change the

Re: moved on to a kernel cmem problem

2009-04-12 Thread Mat Laibowitz
After trying to play around with the memory map some more, I did a little more digging. It seems that the function that fails, according to the oops, is SYNC_SpinLockStartEx, which is in the dsplink source file sync.c located in gpp/src/osal/Linux/2.6.18. Considering that the folder is called

Re: moved on to a kernel cmem problem

2009-04-12 Thread Mat Laibowitz
Changing the mutex functions to rt_mutex functions did not help, neither did include mutex.h. I also tried following the instructions on the wiki here: http://tiexpressdsp.com/index.php?title=Building_DSPLink_with_kbuild and this will successfully build the dsplink, but it still exits with a

RE: moved on to a kernel cmem problem

2009-04-12 Thread Kamoolkar, Mugdha
Mat, We have verified DSPLink with 2.6.18+ versions (notably 2.6.22 and 2.6.23, and later even latest GIT versions). There is no issue of the sort that you have mentioned below. The folder says 2.6.18 because there's no difference as far as DSPLink is concerned between 2.6.18 and later