Difficulty compiling linux-psp04.00.00.12 with sound drivers

Hi,

What commands are you using for the kernel compilation? Are you using the defconfig as mentioned in the user-guide http://processors.wiki.ti.com/index.php/DM816x_C6A816x_AM389x_PSP_User_Guide#Compiling_Linux_Kernel?

Regards,

Vaibhav

what I have done is use the defconfig (as lsited in the wiki link) and added features as I needed them. Features, such as swap, sound and so on.

Hi,

The defconfig has audio support compiled in. Most likely there's a conflict in the features that you are trying to add. Can you list what additional features you are looking for.

Regards,

Vaibhav

Hi Vaibhav

My computer died and installed windows 7 and am having really difficult time posting to these responses. Like I said at first, I was trying to install the ALSA SOC under the sound drivers. I enabled these after configuring with the defconfig for the ti81xx-evm board. I used menuconfig to enable these new options. When the compilation starts to link (LD .tmp_vmliinux1), it starts complaining about functions not being defined:  functions such as:  ”omap_get_dma_src_pos,”  “omap_set_dma params,” and “omap_pcm_hw_free.”  The compilation process at this time points its finger at the file sound/last.c.

 Furthermore, when the correct dma.h is included these problems of undefined functions disappear; however, this is when code-sourcery starts complaining about the external structures and external variables contained within the one function in last.c not being defined; thus, it is evident that this file is missing some includes. In order for me to use your SDK for the ALSA SOC, I need to know the headers and their appropriate paths that sound/last.c needs to compile. At least this is what the behavior indicates.

Though the defconfig has sound features compiled in; it is the defconfig that I originally used and as I need features added such as ALSA SOC I add them. ALSA SOC is the only feature I added (added per the Texas Instruments Document: DM816xx_C6A81xx_AM38xx_Audio_Driver_User_Guide.pdf) .that has given me any abnormal errors or undesirable warnings during the compilation process.

By default, the sound drivers (at least according to menuconfig were not implemeted) What drivers I have added are swap support, tiler support, highmem, devtempfs, scsi support along with scsi USB. None of these should affect the outcome of the sound drivers. Since I hand built my rootfs (including my own cross compiler) all the way up to having Firefox running, I believe, I am doing something correct. There are just a few glitches I am working on sound and memory configuration - memory being the more difficult of the two. It seems that memory configuration is one subject most people avoid - they tend to repeat what already has been said - that being:  "You figure it out!" ;)

Harry

Hi Harry,

Harry Crews said:

 ”omap_get_dma_src_pos,”  “omap_set_dma params,” and “omap_pcm_hw_free.” 

This seems to indicate that you have selected some of the ASoC options under OMAP. The sound support for DM816x is present under sound/soc/davinci/ only.

I am not sure why you are trying to include the OMAP ASoC code in the kernel.

Harry Crews said:

ALSA SOC is the only feature I added (added per the Texas Instruments Document: DM816xx_C6A81xx_AM38xx_Audio_Driver_User_Guide.pdf) .that has given me any abnormal errors or undesirable warnings during the compilation process.

Are you saying that when you follow the instructions in the document you get all these errors?

Harry Crews said:

By default, the sound drivers (at least according to menuconfig were not implemeted)

I'll check up on this.

Harry Crews said:

Since I hand built my rootfs (including my own cross compiler) all the way up to having Firefox running, I believe, I am doing something correct.

Nice to know :)

Harry Crews said:

memory configuration is one subject most people avoid - they tend to repeat what already has been said - that being:  "You figure it out!" ;)

I disagree here. There's an app note which describes the DDR3 setup process in great detail. There also a few forum posts where folks mentioned the issues that they were having and i believe they were all resolved.

If you having any issues with the memory configuration please create a new post describing the issue.

Regards,

Vaibhav

Hi Again

In re:

1: I went through the above mentioned document and there is no mention of the Davinci drivers nor is there any mention of the Omap drivers.

2: I am using the PSP kernel version 04.00.00.12.  I am not sure how to enable the DaVinci drivers.  If I change the platform from Omap to Davinci all support

    for the ti816x board is disabled.  So if there is another way of enabling the Davinci sound drivers that do not disable the evm's support would you enlighten me?

3: yes, by following the above document I get all of those errors.

Harry

BTW thanks for the non-standard response

Harry,

Now this is really strange. I just checked locally and audio support is compiled into the kernel in 04.00.00.12.

Harry Crews said:

I went through the above mentioned document and there is no mention of the Davinci drivers nor is there any mention of the Omap drivers.

Correct set of drivers are already selected in the defconfig and should not require any change for audio support. Sorry for creating the confusion in the first place.

Harry Crews said:

by following the above document I get all of those errors.

Don't you see the following being already selected?

<*> SoC Audio for the TI81XX chip
<*> SoC Audio support for TI81XX EVM

Hi

Here is what I did.  I am running a quad core I5, so don't do this if your pc does not have multiple processors or you'll be doing this all day long.

I started out with the ti816x_evm_defconfig - checked the settings in menuconfig and yes ALSA soc is enbled.  I then built config without any modifications.  It built perfectly.  Then with one modification at a time I rebuilt the kernel. 

swap

highmem

tiler

scsi

graphics ( a few changes)

and then usb

eventually what I found is enabling drivers->USB->Gadgets without enabling OTG support causes the above errors.  enabling OTG with GADGETS still results in build errors, but not the same ones. and there the programmers will find a bug.

thanks for your rapport

Harry