You might want to patch the file with 
http://arago-project.org/git/people/?p=sajesh/arago-dvsdk-integration.git;a=blob;f=recipes/ti/files/dm355mm.patch;h=6ee6064f5afc56c914a88722a4678a7d699a3ca2;hb=e7d033861d6e89703525a501f619c132cde4a15c
 

Regards,
Sajesh

-----Original Message-----
From: davinci-linux-open-source-boun...@linux.davincidsp.com 
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of 
Tivy, Robert
Sent: Tuesday, December 15, 2009 7:16 PM
To: Paul Stuart; Linux on DaVinci
Subject: RE: Where is dm350mmap_reply_mutex defined?

Perhaps you missed an earlier build error related to it.  My (old) copy of 
dm350mmap.c has:
static DECLARE_MUTEX_LOCKED (dm350mmap_reply_mutex);

You can know that it *should* be defined in dm350mmap.c because it's got the 
dm350mmap perfix.

Regards,

- Rob 

> -----Original Message-----
> From: davinci-linux-open-source-boun...@linux.davincidsp.com
> [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com
> ] On Behalf Of Paul Stuart
> Sent: Tuesday, December 15, 2009 3:11 PM
> To: Linux on DaVinci
> Subject: Where is dm350mmap_reply_mutex defined?
> 
> Hi,
>  Can't rebuild the DVSDK's dm350mmap.ko because 
> "dm350mmap_reply_mutex" is undefined.
> 
> (dm350mmap.ko seems to ship with the DVSDK precompiled)
> 
> Can't find it (dm350mmap_reply_mutex) in the DVSDK sources, git, 
> arago, or montavista kernels. Any leads?
> 
> Thanks!
> Paul
> _______________________________________________
> Davinci-linux-open-source mailing list 
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> 
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to