I was only replying to Panchy's original question. I wasn't trying to
lash out at you at all. Sorry if it came out like that.
BJ
Tivy, Robert wrote:
I'm just speaking in general as to why one might not need to use threads on a
DM355.
- Rob
-----Original Message-----
From: bj [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 9:58 AM
To: Tivy, Robert
Cc: Panchy Rivas; [email protected]
Subject: Re: Is there a reason why the DM6446 demos use
threads and the demos in the DM355 don't?
What version of the sdk are you using? We're running
dvsdk_1_30_00_40 and the dm355 demos certainly make use of threads.
BJ
Tivy, Robert wrote:
One reason would be that the DM355 doesn't have a DSP so there's no
other processor to wait on. In DM6446, a thread submitting
a frame to
the DSP codec will block on completion of that frame, so there are
some idle ARM CPU cycles to take advantage of while the one
thread is
blocked. On DM355, there is no blocking in a thread
submitting frames
to the codec (on the ARM) since the submitting thread just
transitions
to the codec processing and then returns back to the
submitting code.
- Rob
--------------------------------------------------------------
----------
*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On
Behalf Of *Panchy Rivas
*Sent:* Wednesday, October 29, 2008 1:52 PM
*To:* [email protected]
*Subject:* Is there a reason why the DM6446 demos use
threads and
the demos in the DM355 don't?
Is there a reason why the DM6446 demos use threads and
the demos in
the DM355 don't?
Thanks
Panchy Rivas
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
