From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4FFF37FF.9080406@xenomai.org> Date: Thu, 12 Jul 2012 22:47:59 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4FFF33F9.9020000@xenomai.org> In-Reply-To: <4FFF33F9.9020000@xenomai.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Xenomai 2.6.1 on beaglebone (TI AM3359 SoC) List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephan Kappertz Cc: xenomai@xenomai.org On 07/12/2012 10:30 PM, Gilles Chanteperdrix wrote: > On 07/12/2012 09:54 PM, Stephan Kappertz wrote: >> OMAP clockevent source: GPTIMER2 at 24000000 Hz >> OMAP clocksource: GPTIMER1 at 32768 Hz >> I-pipe, 0.032 MHz clocksource > > This is wrong, normally, you should have something like: > [ 0.000000] OMAP clockevent source: GPTIMER2 at 13000000 Hz > [ 0.000000] OMAP clocksource: GPTIMER3 at 13000000 Hz > [ 0.000000] I-pipe, 13.000 MHz clocksource > > This is ensured by this piece of code in arch/arm/mach-omap2/timer.c: > #ifndef CONFIG_IPIPE > OMAP_SYS_TIMER_INIT(3, 1, OMAP3_CLKEV_SOURCE, 2, OMAP3_MPU_SOURCE) > #else > OMAP_SYS_TIMER_INIT(3, 2, OMAP3_CLKEV_SOURCE, 3, OMAP3_MPU_SOURCE) > #endif > > So, my guess is that you have some other patch changing this. > Sending your .config would help. Because you probably have CONFIG_OMAP_32K_TIMER on, which should not be normally possible. -- Gilles.