Re: [Xenomai] Porting Ipipe to new ARM SoC (Xilinx Zynq)

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

On 02/13/2013 06:57 PM, mfornero@aanddtech.com wrote:

> Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote on
> 02/10/2013 09:23:22 AM:
>> Hi Stefan, Matthew,
>>
>> I do not know if you managed to get the I-pipe working on Zynq.
>> You may have missed it, but it may be very important for debugging the
>> issues you encounter with the I-pipe port on Zynq, printk from primary
>> domain in I-pipe patches for Linux 3.4 and 3.5 does not work. So, if
>> you are debugging with printk, it may lead you to false conclusions.
>> You should apply the following patch (it has been pushed in the
>> for-core-3.5.7 branch of the ipipe-gch git):
>>
>> diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
>> index 3b86167..f77ef11 100644
>> --- a/arch/arm/kernel/smp.c
>> +++ b/arch/arm/kernel/smp.c
>> @@ -440,7 +440,7 @@ void __ipipe_ipis_alloc(void)
>>        return;
>>  
>>     /* __ipipe_first_ipi is 0 here  */
>> -   ipi_nr = IPI_IPIPE_FIRST + IPIPE_LAST_IPI;
>> +   ipi_nr = IPI_IPIPE_FIRST + IPIPE_LAST_IPI + 1;
>>  
>>     for (virq = IPIPE_IPI_BASE; virq < IPIPE_IPI_BASE + ipi_nr; virq++) {
>>        _virq = ipipe_alloc_virq();
>>
> 
> Hi All,
> 
> It seems that the issues I was having with using the twd as a clockevent
> were related to my defconfig.
> Comparing mine with Stefan's revealed a few key differences, some of
> which were likely fatal. After making the following changes,
> I am able to run using the twd for the clockevent instead of the xttcps:
> 
> CONFIG_NO_HZ=n
> CONFIG_HOTPLUG_CPU=n


These two ones should be harmless

> CONFIG_CPU_FREQ=n


This one is definitely not harmless is you select another cpufreq
governor than "performance".

> CONFIG_MPCORE_WATCHDOG=n


I do not know about this one.
-- 
                                                                Gilles.