summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a84153c)
raw | patch | inline | side by side (parent: a84153c)
author | Prasad Konnur <prasad.konnur@ti.com> | |
Mon, 30 Jan 2012 11:46:29 +0000 (17:16 +0530) | ||
committer | Prasad Konnur <prasad.konnur@ti.com> | |
Mon, 30 Jan 2012 11:46:29 +0000 (17:16 +0530) |
release_notes_edma3_lld_02_11_04.html | patch | blob | history |
index 175af6e69bce14151b219b1e030239f902f98c99..2c16203adb6122b8427903b10d98b21d6faa0689 100755 (executable)
EDMA3LLD being a low level driver the address translation is not done by this. It is expected that the application
will provide the addresses, corresponding to EDMA memory map to configure in PARAM.
</p>
+</a>
+ <a name="Introduction"> <li> <FONT COLOR ='RED'><b>All resources are allocated to all cores in default sample configuration files of EDMA3 LLD</b> </FONT></li>
+<br>The EDMA resources like Channels, PaRAMs and TCCs which are shared by multiple cores (Ex: in Netra and Cenaturus),
+The default configuration file allocates all the resources to every core since the resource split is application dependant.
+The applications using EDMA3LLD should appropriately allocate the resources in the config files and build EDMA3LLD libraries.
+</p>
</a>
</ul>
<a name="Documentation">