On Mon, 2018-12-24 at 01:07 +0200, Daniel Baluta wrote:
Hi,
In src/platform/baytrail/baytrail.x.in we have:
vector_double_text : org = XCHAL_DOUBLEEXC_VECTOR_PADDR, len = SOF_MEM_VECT_TEXT_SIZE sof_text_start : org = XCHAL_DOUBLEEXC_VECTOR_PADDR + SOF_MEM_VECT_SIZE,
Is the address of sof_text_start correct here?
vector_double_text ends at: XCHAL_DOUBLEEXC_VECTOR_PADDR + SOF_MEM_VECT_TEXT_SIZE
but sof_text_start (which is the next segment in memory) doesn't start immediately after vector_double_text because
SOF_MEM_VECT_SIZE = SOF_MEM_VECT_TEXT_SIZE + SOF_MEM_VECT_LIT_SIZE
so there is a gap of SOF_MEM_VECT_LIT_SIZE (4 bytes) between vector_double_text and sof_text_start.
Is this on purpose?
This should be OK, all section should start on 4 byte boundaries on xtensa. Xtensa usually has gaps between each section so this gap was probably copy and pasted.
Liam
thanks, Daniel. _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware