Building DSPLink for Integra

I'm going to try this, but I have no idea if it is correct:

n5ac@N5AC-U11:~/dsplink_linux_1_65_01_06/dsplink/config/bin$ perl dsplinkcfg.pl --platform=OMAP3530 \
 --nodsp=1 --dspcfg_0=OMAP3530SHMEM --dspos_0=DSPBIOS5XX --gppos=OMAPLSP --comps=ponslrmc

defined(%hash) is deprecated at dsplinkcfg.pl line 2069.
 (Maybe you should just omit the defined()?)
defined(%hash) is deprecated at dsplinkcfg.pl line 2574.
 (Maybe you should just omit the defined()?)


 Welcome to DSP/BIOS(TM) Link Configuration Utility
------------------------------------------------------

 !!DSPLINK will be configured for Build OS: LINUX!!

 !!DSPLINK Directory : /home/n5ac/dsplink_linux_1_65_01_06/dsplink!!

=========================================================
Chosen configuration is as follows:

Chosen platform:
 Identifier: OMAP3530
 Description: OMAP3530 SoC - C64P DSP interfaced directly to ARM Cortex-A8
 This platform does not support multi DSP scenario

No of DSPs: 1

Chosen combination for DSP0:
 Identifier : OMAP3530
 DSP Description : On-Chip DSP of OMAP 3530 SoC
 Physical Interface (PHY): OMAP3530SHMEM
 PHY Description : Shared Memory Physical Interface

Chosen DSP OS for DSP0:
 Identifier: DSPBIOS5XX
 Description: DSP/BIOS (TM) Version 5.XX

****************** ADVICE !!! *************************** 
Binaries for DSP can be generated at preferred location 
For example: --dsp0_temp=/home/dsplink/dsp<#>/bin

Chosen GPP OS for selected DSP(s):
 Identifier: OMAPLSP
 Description: OMAP LSP for OMAP2530 and OMAP3530

****************** ADVICE !!! *************************** 
Binaries for GPP can be generated at preferred location 
For example: --gpp_temp=/home/dsplink/gpp/bin

Chosen Components for DSPLink:
 USE_PROC = 1
 USE_NOTIFY = 1
 USE_POOL = 1
 USE_MPCS = 1
 USE_MPLIST = 1
 USE_RINGIO = 1
 USE_MSGQ = 1
 USE_CHNL = 1

****************** ADVICE !!! *************************** 
To enable trace use option: --trace=1
Provided: 
Assuming trace disable and continuing...

****************** ADVICE !!! *************************** 
To enable legacy support use option: --legacy=1
Provided: 
Assuming legacy support disable and continuing...

****************** ADVICE !!! *************************** 
To enable DSP TSK mode select: --DspTskMode=1
Provided: 
Assuming SWI mode enabled and continuing...
=========================================================

Configuration done successfully!!
Generating CURRENTCFG.MK file...
Generating multimake script...
Generating CFG_system.c File...
Generating GPP RTSC xdc file...
Generating DSP RTSC xdc file...
=========================================================
Please edit the following files for toolchains, kernel sources, etc changes.
GPP side distribution file: $DSPLINK/make/Linux/omap3530_2.6.mk
GPP side distribution file: $DSPLINK/gpp/src/Rules.mk
DSP side distribution file: $DSPLINK/make/DspBios/c64xxp_5.xx_linux.mk
==========================================================
Users consuming DSPLINK as XDC package, Need to do the following.
cd into the $(DSPLINK)/dsp directory and run: 
 $(XDC_INSTALL_DIR)/xdc clean 
 $(XDC_INSTALL_DIR)/xdc .interfaces 
cd into the $(DSPLINK)/gpp directory and run: 
 $(XDC_INSTALL_DIR)/xdc clean 
 $(XDC_INSTALL_DIR)/xdc .interfaces 
==========================================================
n5ac@N5AC-U11:~/dsplink_linux_1_65_01_06/dsplink/config/bin$ 

DSPLink does not support the DM8168/C6A8168:

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/DSPLink/1_65_01_06/exports/dsplink_linux_1_65_01_06/dsplink_1_65_01_06_ReleaseNotes.html#Device_Support

If you're trying to use c6ezaccel with that device then you will need the c6ezaccel 2.x code branch which is shipped inside the SDK according to here:

http://processors.wiki.ti.com/index.php/C6EZAccel#Download

The DM8168/C6A8168 EZSDK uses ezaccel 2.x in conjunction with syslink 2.x (not dsplink).  So the support you require would be part of syslink.

OK I expected to have to build them because of this comment in the "Introduction to C6Accel" document under "How to Install C6Accel":

Assumption: The Build step assumes that the linux kernel, cmem and dsplink module have been pre-built. If the are
not built users are expected to build those dependencies before building the C6accel package.

I'll see if I can figure how to build it without these pieces -- thanks.

Steve