From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 1 Dec 2014 16:29:21 +0100 From: Gilles Chanteperdrix Message-ID: <20141201152921.GI23220@hermes> References: <20141128111325.GD5069@hermes> <20141128182141.GB4817@hermes> <20141201143957.GH23220@hermes> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Xenomai] Section mismatch - Porting Xenomai to linux-xlnx-V14.5 zynq SoC List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Sini Cc: xenomai@xenomai.org 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. 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? -- Gilles.