[Xenomai] Xenomai on Atmel SAMA5D3 with a 3.14 kernel
gilles.chanteperdrix at xenomai.org
Thu Jun 12 19:57:27 CEST 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 06/12/2014 05:03 PM, Maxime Ripard wrote:
> On Thu, Jun 12, 2014 at 10:37:11AM +0200, Gilles Chanteperdrix
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> On 06/12/2014 09:54 AM, Maxime Ripard wrote:
>>> On Wed, Jun 11, 2014 at 08:16:15PM +0200, Gilles Chanteperdrix
>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>> On 06/11/2014 11:25 AM, Maxime Ripard wrote:
>>>>> On Tue, Jun 10, 2014 at 12:01:36PM +0200, Gilles
>>>>> Chanteperdrix wrote:
>>>>>> If you compile the kernel without I-pipe and Xenomai
>>>>>> support and enable the tcb_clksrc clocksource driver does
>>>>>> it work?
>>>>> Yep, with the exact same config, except for CONFIG_IPIPE
>>>>> and CONFIG_XENOMAI being disabled, it boots fine.
>>>> Read again, I am not insterested in exactly the same config,
>>>> I am interested in the a config with tcb_clksrc clocksource,
>>>> which is disabled by CONFIG_IPIPE. Only if you enable this
>>>> clocksource do you get to use the atmel_tclib code.
>>> Let me rephrase then. It works with the exact same config, with
>>> CONFIG_IPIPE and CONFIG_XENOMAI disabled, and
>>> CONFIG_ATMEL_TCB_CLKSRC enabled.
>> Then I would tend to think that the clocksource is not your
>> problem and repeat that you should check everything else in the
>> porting guide.
> Ok. I will.
On my side, I will try and remove the need for at91_ipipe_early_init,
and get the timer working for 32 bits (I will need you to test the
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the Xenomai