On Fri, Nov 28, 2014 at 2:03 PM, John Sini <[email protected]> wrote:
> > > On Fri, Nov 28, 2014 at 12:13 PM, Gilles Chanteperdrix < > [email protected]> wrote: > >> On Fri, Nov 28, 2014 at 12:03:09PM +0100, John Sini wrote: >> > Hello, >> > >> > I am new with Xenomai and I am trying to port it to linux-xlnx-V14.5 >> zynq >> > as suggested on the following site: >> > >> > http://www.wiki.xilinx.com/Xenomai+for+Zynq >> > >> > Patches that I have applied(in the following order) >> > >> > >> > *ipipe-core-3.8-zynq-pre.patch* >> > *ipipe-core-3.8-arm-1.patch* >> > *ipipe-core-3.8-zynq-post.patch* >> > >> > >> > I have disabled the support of RPMsg ((remoteproc) and of CPU_HOTPLUG >> > prior to compiling the kernel(I configured the kernel as suggested on >> > the aforementioned website). I get getting the following warnings: >> > >> > WARNING: vmlinux.o(.text+0x106b4): Section mismatch in reference from >> > the function __ipipe_tsc_register() to the variable >> > .init.text:__kuser_helper_end >> > The function __ipipe_tsc_register() references >> > the variable __init __kuser_helper_end. >> > This is often because __ipipe_tsc_register lacks a __init >> > annotation or the annotation of __kuser_helper_end is wrong. >> > >> > WARNING: vmlinux.o(.text+0x106b8): Section mismatch in reference from >> > the function __ipipe_tsc_register() to the variable >> > .init.text:__ipipe_tsc_area_start >> > The function __ipipe_tsc_register() references >> > the variable __init __ipipe_tsc_area_start. >> > This is often because __ipipe_tsc_register lacks a __init >> > annotation or the annotation of __ipipe_tsc_area_start is wrong. >> >> For this, you can do what the warning says, add the __init attribute >> to the __ipipe_tsc_register function. This has been made in later >> patches. 3.8 is old, we do not have the necessary resources to >> maintain all past versions of the I-pipe patch at all times. >> > > Thank you for your answer. I have found __ipipe_tsc_register function > in: > > */arch/arm/kernel/ipipe_tsc.c* > I guess it's like this: > * void __init __ipipe_tsc_register(struct __ipipe_tscinfo *info) { struct > ipipe_tsc_value_t *vector_tsc_value; unsigned long *tsc_addr; __ipipe_tsc_t > *implem; unsigned long flags; int registered; char *tsc_area;* > > > *#if !defined(CONFIG_CPU_USE_DOMAINS) ......etc ..* > > > *and in the header file:* > > */arch/arm/include/asm/ipipe.h* > > *void **__init __ipipe_tsc_register**(struct __ipipe_tscinfo *info); * > > > Are these only two places where I have to add the __init attribute and > how exactly would you add it? > > > >> >> > >> > WARNING: vmlinux.o(.text+0x2ea760): Section mismatch in reference from >> > the function vexpress_sysreg_probe() to the function >> > .init.text:vexpress_sysreg_setup() >> > The function vexpress_sysreg_probe() references >> > the function __init vexpress_sysreg_setup(). >> > This is often because vexpress_sysreg_probe lacks a __init >> > annotation or the annotation of vexpress_sysreg_setup is wrong. >> >> This probably has nothing to do with Xenomai. >> >> > >> > >> > Can any of you help me how to fix these warnings? I have seen the same >> > problem here: >> > >> > http://www.xenomai.org/pipermail/xenomai/2013-October/029390.html >> > >> > But I have disabled all necessary options in the kernel config and >> > still get these warnings. >> >> what necessary option? >> >> > Are there any new Xenomai patches that work with some newer version of > Kernel? IIRC, xenomai 2.6.4 also uses xilinx-v14.5 and same patches, right? > > > Many thanks for your previous answers. > > Best, > John > > > > -- >> Gilles. >> > > _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
