I don't really understand this yet, but maybe some background will help [at least!] both of us...
In general, the ARM-side Link config can be done in 1 of 2 use cases: 1. Static config. The config struct is constructed in a .c file and built _into_ the Link binaries during the DSP Link build. The pre-built config is used when, at run time, PROC_setup() is called with a NULL config struct ptr. 2. Dynamic config. The config struct is crafted at run time and passed into Link via the PROC_setup() call. Codec Engine uses the 2nd model under the hood (during Engine_open()). Since the memory map is part of this config, and different DSP images can potentially have different memory maps, this approach lets Codec Engine load different images without forcing a rebuild of anything. (BTW, this memory map info is some of the gems we scrape out of the DSP build during Engine.createFromServer()). All that to say I don't know why changing _your_ static LINKCFG_Dsp struct (which might be used in use case #1) has any affect in a Codec Engine-based system (which uses use case #2). :? Chris > -----Original Message----- > From: Brian Rhodes [mailto:b...@acdstar.com] > Sent: Thursday, June 25, 2009 9:14 AM > To: Brian G Rhodes > Cc: Ring, Chris; davinci-linux-open-source@linux.davincidsp.com > Subject: Re: Codec Engine 2_23_01 Failure to load Server > > Brian G Rhodes wrote: > > Chris, > > > > I found that my map is proper, and the issue is elsewhere. > It looks > > like the LINKCFG_Dsp structure. The av5T ipc_dsplink > library which is > > being linked with the application seems to have some duplicate > > symbols. I modified the LINKCFG_Dsp in dsplink to change > the name and > > found that the settings from the ipc dsplink library are there as > > well. objdump does list duplicate symbols for the dsp config. The > > alignment after the dsp power control field is off 4 bytes > in the data > > dsplink gets from the application. > I was able to get the system working by adding a 4 byte offset in the > LINKCFG_Dsp structure for the kernel dsplink component after the dsp > power control field. Is this possibly happening because I > built dsplink > kernel module using kbuild? > > _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
