Hi Greg,
On 2018-05-30 18:46, Greg Gallagher wrote:
I agree, after the first run of building the images myself I think
having the user generate the images would make more sense. I'm
looking into doing that with an existing tool I think yocto may be a
good choice.
In case you need some help
I think there's still some ongoing work in both ARM and x86, Philippe
and Jan may be able to comment more on the timeline. You can directly
clone the ipipe-arm tree and evaluate if it would work on your
platform. There are still some issues with beaglebone/beagleboard in
4.14 that I'm looking
+ Aisheng, Nitin and Leonard
On Thu, May 31, 2018 at 03:06:16PM +0200, Philippe Gerum wrote:
> On 05/31/2018 03:01 PM, Philippe Gerum wrote:
> > On 05/31/2018 09:25 AM, Abel Vesa wrote:
> >> The problem is the fact that the arm twd irq (for example) is masked on
> >> that
> >> specific core
On 05/31/2018 03:01 PM, Philippe Gerum wrote:
> On 05/31/2018 09:25 AM, Abel Vesa wrote:
>> The problem is the fact that the arm twd irq (for example) is masked on that
>> specific core inside gic, but the ipipe is locking it globally.
>>
>> According to GIC architecture specification
>>
>>
On 05/31/2018 09:25 AM, Abel Vesa wrote:
> The problem is the fact that the arm twd irq (for example) is masked on that
> specific core inside gic, but the ipipe is locking it globally.
>
> According to GIC architecture specification
>
>
Hello,
now we are testing ipipe 4.14 for both platforms.
Everything seems to be ok.
Is there a schedule/roadmap for a release?
Thanks
Jimmy
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
The problem is the fact that the arm twd irq (for example) is masked on that
specific core inside gic, but the ipipe is locking it globally.
According to GIC architecture specification
https://www.cl.cam.ac.uk/research/srg/han/ACS-P35/zynq/arm_gic_architecture_specification.pdf
Section 2.2.1
