On 07.01.21 19:27, Jan Kiszka via Xenomai wrote:
> On 07.01.21 18:56, Jan Kiszka via Xenomai wrote:
>> On 17.12.20 19:02, Philippe Gerum wrote:
>>> From: Philippe Gerum
>>>
>>> Although there are significant commonalities between the I-pipe and
>>> Dovetail when it comes to dealing with synchronou
On 07.01.21 18:46, Jan Kiszka via Xenomai wrote:
> On 18.12.20 10:49, Q. Gylstorff wrote:
>> From: Quirin Gylstorff
>>
>> Add xenomai 3.1 to the build and test pipeline of xenomai-images.
>>
>> Add parent_child pipelines[1] to have a better overview of the builds.
>>
>> [1]: https://docs.gitlab.co
On 07.01.21 18:56, Jan Kiszka via Xenomai wrote:
> On 17.12.20 19:02, Philippe Gerum wrote:
>> From: Philippe Gerum
>>
>> Although there are significant commonalities between the I-pipe and
>> Dovetail when it comes to dealing with synchronous kernel events,
>> there is no strict 1:1 mapping betwe
On 17.12.20 19:02, Philippe Gerum wrote:
> From: Philippe Gerum
>
> Although there are significant commonalities between the I-pipe and
> Dovetail when it comes to dealing with synchronous kernel events,
> there is no strict 1:1 mapping between the two kernel interfaces.
>
> As an initial step,
On 18.12.20 10:49, Q. Gylstorff wrote:
> From: Quirin Gylstorff
>
> Add xenomai 3.1 to the build and test pipeline of xenomai-images.
>
> Add parent_child pipelines[1] to have a better overview of the builds.
>
> [1]: https://docs.gitlab.com/ee/ci/parent_child_pipelines.html
>
> You can see an
On Thu, Jan 7, 2021 at 10:53 AM hailong via Xenomai
wrote:
> At 2021-01-04 01:38:04, "Philippe Gerum" wrote:
> >
> >Hailongliu via Xenomai writes:
> >
> >> Hi,
> >>
> >> I learned the "Common Xenomai Platform" program from this mail-list and
> wiki
> >> of project Xenomai. This is a very attrac
At 2021-01-04 01:38:04, "Philippe Gerum" wrote:
>
>Hailongliu via Xenomai writes:
>
>> Hi,
>>
>> I learned the "Common Xenomai Platform" program from this mail-list and wiki
>> of project Xenomai. This is a very attractive plan, as it will port Xenomai
>> for
>> recent LTS kernel(v5.10).
>>
>> I
On 02.01.21 10:33, Philippe Gerum wrote:
> From: Philippe Gerum
>
> The I-pipe and Dovetail differ only marginally with respect to syscall
> handling. Abstract only the few details we need to cope with both
> interfaces.
>
> No functional change is introduced.
>
> Signed-off-by: Philippe Gerum
On 02.01.21 10:33, Philippe Gerum wrote:
> From: Philippe Gerum
>
> No functional change is introduced.
>
> Signed-off-by: Philippe Gerum
> ---
> .../cobalt/kernel/ipipe/pipeline/wrappers.h | 25 +++
> .../cobalt/include/linux/xenomai/wrappers.h | 23 -
> ke
On 02.01.21 10:33, Philippe Gerum wrote:
> From: Philippe Gerum
>
> This interface is pointless with Dovetail whose applications directly
> refer to the wallclock time exported through the common vDSO.
>
> No functional change is introduced.
>
> Signed-off-by: Philippe Gerum
> ---
> include/c
On 02.01.21 11:38, Leandro Bucci via Xenomai wrote:
> Hello and happy new year to all. I wanted to ask you in detail what this
> line means:
>
> isolcpus=0,1 xenomai.supported_cpus=0x3
>
> I understand that 2 CPUs are isolated. (I'm working on a Raspberry). But in
> what sense are they isolated?
I see. Thank you for your detailed explanation.
My understanding of this question is at a different level with your
generous help.
>You can guarantee _average_ data for I/O to storage devices, like a
>guaranteed sustained throughput (*), but you will not be able to
>guarantee any hard real-time b
Dear 孙世龙 sunshilong,
In message
you wrote:
> >depends on your use case, maybe possible to add a raw disk, only used by
> >the time critical code?
> It seems a good solution.
> It's possible to add a raw disk.
This will not help you at all. The key problem here is that common
storage devices (c
13 matches
Mail list logo
