Actually, don't worry about me here.. I have figured it out and noticed that the videnc_copy example actually uses this.
With the UK/US time difference I find I can sometimes save a day's scratching about if I post the question earlier rather than later. But for anyone that wants to know the answer in the future... the CE does implement the "calling side" code, just have a look at the videnc_copy example. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben White Sent: 06 November 2007 13:12 To: [email protected] Subject: DMAN3 with Codec Engine Hello again! Just a quick question this time. I am wanting to utilise the EDMA controller in my algo. As I am using Codec Engine, I naturally want to use the DMAN3 and ACPY3 FC modules. My question refers to where the DMAN3 "client-side" code lives, or should live. Think about DSKT2 - from an algorithm and a client perspective, all the DSKT2 magic is encapsulated within the codec engine. I don't have to write any DSKT2 code in my algo or my client app, yet the CE will use it to take care of my memory for me, ask me about how much memory I want to allocate, and ask me where I want to allocate it (through algAlloc, etc). Is this the same for DMAN3? Does the CE magically call my DMAN3 functions (e.g. dmaGetChannels) via the IAlg vtable? Or.... As I suspect, does my client app have to be the "caller" of the DMAN3 functions, and not the CE as for DSKT2? I can't find any documentation or examples that would suggest that the CE is the "caller" of the DMAN3 funcs, but since it does such a nice job with the DSKT2, I wondered if it would do the same for me again with DMAN3? Thanks, Ben
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
