Re: [Xenomai] Section mismatch - Porting Xenomai to linux-xlnx-V14.5 zynq SoC

[Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>]

On Wed, Dec 03, 2014 at 02:32:12PM +0100, John Sini wrote:
> On Mon, Dec 1, 2014 at 5:15 PM, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
> 
> > On Mon, Dec 01, 2014 at 04:45:03PM +0100, John Sini wrote:
> > > On Mon, Dec 1, 2014 at 4:29 PM, Gilles Chanteperdrix <
> > > gilles.chanteperdrix@xenomai.org> wrote:
> > >
> > > > On Mon, Dec 01, 2014 at 04:26:47PM +0100, John Sini wrote:
> > > > > On Mon, Dec 1, 2014 at 3:39 PM, Gilles Chanteperdrix <
> > > > > gilles.chanteperdrix@xenomai.org> wrote:
> > > > >
> > > > > > On Mon, Dec 01, 2014 at 03:35:51PM +0100, John Sini wrote:
> > > > > > >  Hi,
> > > > > > >
> > > > > > >
> > > > > > > Thank you for your reply. I have disabled lockdep by disabling
> > > > following
> > > > > > > two options in Kernel configuration :Lock debugging:prove locking
> > > > > > > correctness and  Lock debugging: detect incorrect freeing of live
> > > > locks.
> > > > > > > The problem that i am facing now is:
> > > > > >
> > > > > > Does the exact same .config file work on an unpatched kernel?
> > > > > >
> > > > > > Just checked and I got the same error.
> > > >
> > > > So, before trying and compiling Xenomai with a configuration file,
> > > > please try and get a working configuration for your kernel, without
> > > > Xenomai patch applied.
> > > >
> > > >   Ok, I will do it.
> > >
> > >
> > > > Also, since the Zynq patch is provided by a third party, and not
> > > > part of the patches supported by the mainline I-pipe patch, I do not
> > > > even compile test this patch, so have no working configuration to
> > > > propose.
> > > >
> > > > Maybe the people having proposed the patch could also propose a
> > > > working kernel configuration? That would be nice.
> > >
> > >
> > >
> > >    Can you maybe explain me the errors that *I got i.e. can they be due
> > to
> > > xenomai(kernel panic)*
> >
> > I do not know what you are talking about. If the same configuration
> > on an unpatched kernel has an issue, then the issue certainly has
> > nothing to do with Xenomai, don't you think ?
> >
> >
>   Yeah I do think :) I have just one question concerning this warning that
> I still have(I think it's due to Xenomai as it's about ipipe)
> 
> WARNING: vmlinux.o(.cpuinit.text+0xdc0): Section mismatch in reference from
> the function gt_setup.part.2.constprop.4() to the function
> .init.text:__ipipe_tsc_register()
> The function __cpuinit gt_setup.part.2.constprop.4() references
> a function __init __ipipe_tsc_register().
> If __ipipe_tsc_register is only used by gt_setup.part.2.constprop.4 then
> annotate __ipipe_tsc_register with a matching annotation.
> 
>  - I have already put __init attribute in front of __ipipe_tsc_register
> function in ipipe-core-3.8-arm-1.patch. If I put __init attribute in front
> of the name of  __cpuinit gt_setup function in the same patch - will that
> fix this warning that I have?

I would say so, probably yes.

-- 
					    Gilles.