Hello,
I try to get compiled some xemomai2 kernel modules with native-api to xenomai3
alchemy.
I have build a single kernel xenomai configuration (mercury) with a centos
3.10.0 kernel.
The Makefile from xenomai2 does not work anymore. The Makefiles from xenomai3
demo directory are very complex
On 12/02/2016 12:38 PM, Michael Wisse wrote:
> Hello,
>
> I try to get compiled some xemomai2 kernel modules with native-api to
> xenomai3 alchemy.
> I have build a single kernel xenomai configuration (mercury) with a centos
> 3.10.0 kernel.
>
> The Makefile from xenomai2 does not work anymore.
Hello
Context: I'm using the pSOS interface over the Mercury core (version 3.0.3).
I have a question about option:
–mem-pool-size
described on page
http://xenomai.org/2015/05/application-setup-and-init/
Is the parameter specifying the maximum size that will be used Xenomai
or is this the initial
On 12/02/2016 02:03 PM, Ronny Meeus wrote:
> Hello
>
> Context: I'm using the pSOS interface over the Mercury core (version 3.0.3).
>
> I have a question about option:
> –mem-pool-size
> described on page
> http://xenomai.org/2015/05/application-setup-and-init/
>
> Is the parameter specifying th
On Fri, Dec 2, 2016 at 3:01 PM, Philippe Gerum wrote:
> On 12/02/2016 02:03 PM, Ronny Meeus wrote:
>> Hello
>>
>> Context: I'm using the pSOS interface over the Mercury core (version 3.0.3).
>>
>> I have a question about option:
>> –mem-pool-size
>> described on page
>> http://xenomai.org/2015/05/
Hello,
freshly installed Cobalt 3.0.3 on a BeagleBone Black (ARM Cortex-A8) with
kernel 4.4.35 (rcn:
https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-xenomai-4.4.y
).
When runnig xeno-test I get the below error.
Note that latency test works ok (though the values are a bit high
On 12/02/2016 03:29 PM, Ronny Meeus wrote:
> On Fri, Dec 2, 2016 at 3:01 PM, Philippe Gerum wrote:
>> On 12/02/2016 02:03 PM, Ronny Meeus wrote:
>>> Hello
>>>
>>> Context: I'm using the pSOS interface over the Mercury core (version 3.0.3).
>>>
>>> I have a question about option:
>>> –mem-pool-size
On 12/02/2016 01:33 PM, Philippe Gerum wrote:
I plan to phase out TLSF entirely, which has poor performances with
respect to memory fragmentation (the numbers are actually pretty ugly).
So either we live with the current state of affairs until TLSF is
replaced, or a trivial patch preventing the e