Re: [Xenomai] xenomai/ipipe arm64 port

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2015-08-25 19:54, Jorge Ramirez Ortiz wrote:
> On 08/25/2015 01:36 PM, Jan Kiszka wrote:
>> On 2015-08-25 19:34, Jorge Ramirez Ortiz wrote:
>>> On 08/25/2015 01:07 PM, Jorge Ramirez Ortiz wrote:
>>>> On 08/25/2015 12:13 PM, Jan Kiszka wrote:
>>>>> On 2015-08-25 17:20, Jorge Ramirez Ortiz wrote:
>>>>>> On 08/25/2015 10:08 AM, Philippe Gerum wrote:
>>>>>>> On 08/25/2015 02:13 AM, Don Mahurin wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> We would like to submit our current work on the arm64 port of
>>>>>>>> ipipe/xenomai. We hope that this contribution will encourage further
>>>>>>>> development of arm64 support in ipipe/xenomai.
>>>>>>>>
>>>>>>>
>>>>>>> arm64 support is definitely a high priority item. Thanks for tackling this.
>>>>>>
>>>>>> There are a numbers of cheap (<100USD) and well documented aarch64 boards [1]
>>>>>> that could be used as a reference platform (different SoC vendors)
>>>>>> I'd suggest we use Qualcomm's Dragon 410c.
>>>>>
>>>>> The Qualcomm thing is pretty ugly beast, using a proprietary interrupt
>>>>> controller instead of the standard GIC as strongly recommended by ARM.
>>>
>>>
>>> Looking at the device tree setting it seems to me it is using GICv2
>>>
>>> drivers/irqchip/irq-gic.c
>>>
>>
>> Really? I'm looking at upstream right now, and there is no "arm,gic-*"
>> compatible string - in contrast to the hi6220.
> 
> 
> right, the APQ8016 uses compatible = "qcom,msm-qgic2" handled in
> drivers/irqchip/irq-gic.c
> 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/qcom/msm8916.dtsi?id=refs/tags/v4.2-rc8#n135
> 

Interesting. That /may/ work out smoothly for I-pipe, and it just
doesn't work for virtualization because the "qgic2" lacks GICH and GICV
regions, thus virtualization extensions.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux