From mboxrd@z Thu Jan 1 00:00:00 1970 Resent-Message-ID: <20140612074411.GB18962@lukather> Resent-To: xenomai@xenomai.org Date: Fri, 6 Jun 2014 15:59:12 +0200 From: Maxime Ripard Message-ID: <20140606135912.GJ5765@lukather> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: [Xenomai] Xenomai on Atmel SAMA5D3 with a 3.14 kernel List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Michael Opdenacker , Thomas Petazzoni , Boris Brezillon , Alexandre Belloni , xenomai@xenomai.org, Antoine =?iso-8859-1?Q?T=E9nart?= Hi Gilles, I've been experimenting these days with the i-pipe 3.14 kernel, and current xenomai master branch on the Atmel SAMA5D3 SoC. There's a few issues there, the first one being that at91_ipipe_early_init crashes because of a NULL pointer dereference. This is due to the clk_get_rate call on the clock returned by clk_get(NULL, "mck"). This clk_get call cannot since 3.14 because the clock code has been rewritten, and you can't use clkdev anymore. This is quite simple to fix, and after actually fixing it, you get a more interesting issue: either the timers or the interrupts don't work at all. The first symptom is that it get stuck at the delay loop calibration. Setting the loops per jiffy in the command line make the boot go further, until the switch to the ipipe_tsc clocksource. This actually makes me think that it's more the timers that are broken rather than the interrupts. Changing the timer counter block doesn't solve anything. Do you have an idea of what could be going on? You'll find the boot logs here: http://pastebin.com/58N20Xxs Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: