diff -r 578be2adaf3e -r 307f4279f433 Adaptation/GUID-95A33491-17AC-4F12-948E-A1352ADDA483.dita
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-95A33491-17AC-4F12-948E-A1352ADDA483.dita Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,85 @@
+
+
+
+
+
+ The DMA Framework is made of a PIL and a PSL. You have to write
+a new Platform specific implementation code whenever your hardware
+changes, but the PIL and the platform service API do not change. You should be familiar with the In the diagram below, the classes in green provide the platform
+service API and the classes in blue implement the Platform-specific
+functions (PSL). The following table lists the important files of the
+DMA Framework and what you should do with each of them. This file is the main header file for DMA. Include
+it in the PSL implementation. This file contains the definitions of the PSL classes. Refer to this file for the signature of the PSL functions. This file is the MMP for the PIL. Use it to build
+the .LIB file for the PIL. This file contains the template code for the PSL implementation. Copy it to your variant directory and modify it. This file is the template MMP for the PSL implementation. Copy it to your variant directory and modify it. Use the
+new file to build the DMA Framework (PIL and PSL).
+
To write the PSL for the DMA Framework, do the following:
Copy the template +listed in the above section to your own variant directory (at chip +level or at board level depending on where the DMA hardware is located).
Implement the
Derive the
If necessary,
+derive the
Test the PSL +implementation.