Re: moved on to a kernel cmem problem

2009-04-13 Thread Mat Laibowitz
*Sent:* Monday, April 13, 2009 4:20 AM *To:* davinci-linux-open-source@linux.davincidsp.com *Subject:* Re: moved on to a kernel cmem problem 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

Re: moved on to a kernel cmem problem

2009-04-13 Thread Yusuf Caglar AKYUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mat Laibowitz wrote: I have been over the memory map a dozen times. I have set my mem parameter in the bootargs to as much as 10 megs lower than the start of my cmem region. I have given DSPLINK more than enough space in the codec servers memory

Re: moved on to a kernel cmem problem

2009-04-13 Thread Mat Laibowitz
Yes, a very similar problem indeed. I tried your patch from [1], and the problem did go away. The code no longer crashes with a kernel paging error! This is major progress, thanks. I am still not able to get the video decoder codecs that use viddec2 interface to work, but not at least I have a

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

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: 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
-open-source@linux.davincidsp.com Subject: Re: moved on to a kernel cmem problem 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