On 03/28/2018 07:20 PM, Pintu Kumar wrote:
> On Wed, Mar 28, 2018 at 8:37 PM, Philippe Gerum wrote:
>> On 03/28/2018 09:54 AM, Pintu Kumar wrote:
>>> Hi,
>>>
>>> We are facing one issue on Xenomai-3 on x86_64 system.
>>> Kernel: 4.9.51
>>> ipipe version: 4
>>> #
On Wed, Mar 28, 2018 at 8:37 PM, Philippe Gerum wrote:
> On 03/28/2018 09:54 AM, Pintu Kumar wrote:
>> Hi,
>>
>> We are facing one issue on Xenomai-3 on x86_64 system.
>> Kernel: 4.9.51
>> ipipe version: 4
>> # /usr/xenomai/sbin/version
>> Xenomai/cobalt v3.0.6 -- #5956064
On 03/28/2018 09:54 AM, Pintu Kumar wrote:
> Hi,
>
> We are facing one issue on Xenomai-3 on x86_64 system.
> Kernel: 4.9.51
> ipipe version: 4
> # /usr/xenomai/sbin/version
> Xenomai/cobalt v3.0.6 -- #5956064 (2018-03-20 12:13:33 +0100)
>
> Its a very simple API level test.
> We create a
Le mercredi 28 mars 2018 à 16:16 +0200, Philippe Gerum a écrit :
>
> cobalt_thread_pid(pthread_t) from the internal support library would
> do
> the job. A successful call would denote a cobalt thread, -ESRCH would
> denote a regular (or invalid) pthread.
Seems to work perfectly, thanks.
Hi!
I found in boot log
failed to start lsb apparmor initialization
could it be the problem ?
С уважением и надеждой на сотрудничество,
Шевченко Т.Г.
- Original Message -
From: "Шевченко Тарас Григорьевич"
To: "Greg Gallagher"
On 03/28/2018 04:00 PM, Julien Blanc wrote:
> We're using a mix of regular NPTL posix threads and RT cobalt threads
> in our application, using XDDP communication between them.
>
> In a few places, we need to identify the calling context, ie, whether
> we're being called from a cobalt RT thread
We're using a mix of regular NPTL posix threads and RT cobalt threads
in our application, using XDDP communication between them.
In a few places, we need to identify the calling context, ie, whether
we're being called from a cobalt RT thread or from a regular NPTL
thread, and act accordingly.
My
On 03/28/2018 12:04 PM, Pintu Kumar wrote:
> On Wed, Mar 28, 2018 at 1:44 PM, Julien Blanc wrote:
>> Le mercredi 28 mars 2018 à 13:24 +0530, Pintu Kumar a écrit :
>>> Hi,
>>>
>>> We are facing one issue on Xenomai-3 on x86_64 system.
>>> Kernel: 4.9.51
>>> ipipe version:
Hi,
Any clue on this one?
How to add our own debug printf statements inside xenomai library
function?
Thanks,
Pintu
On Tue, Mar 27, 2018 at 10:08 PM, Pintu Kumar wrote:
> Hi,
>
> How to add our own debug printf statements inside xenomai library
> function, in order to
On Wed, Mar 28, 2018 at 1:42 PM, Philippe Gerum wrote:
> On 03/28/2018 09:54 AM, Pintu Kumar wrote:
>> Hi,
>>
>> We are facing one issue on Xenomai-3 on x86_64 system.
>> Kernel: 4.9.51
>> ipipe version: 4
>> # /usr/xenomai/sbin/version
>> Xenomai/cobalt v3.0.6 -- #5956064
Le mercredi 28 mars 2018 à 13:24 +0530, Pintu Kumar a écrit :
> Hi,
>
> We are facing one issue on Xenomai-3 on x86_64 system.
> Kernel: 4.9.51
> ipipe version: 4
> # /usr/xenomai/sbin/version
> Xenomai/cobalt v3.0.6 -- #5956064 (2018-03-20 12:13:33 +0100)
>
> Its a very simple API level test.
>
On 03/28/2018 09:54 AM, Pintu Kumar wrote:
> Hi,
>
> We are facing one issue on Xenomai-3 on x86_64 system.
> Kernel: 4.9.51
> ipipe version: 4
> # /usr/xenomai/sbin/version
> Xenomai/cobalt v3.0.6 -- #5956064 (2018-03-20 12:13:33 +0100)
>
> Its a very simple API level test.
> We create a
Hi,
We are facing one issue on Xenomai-3 on x86_64 system.
Kernel: 4.9.51
ipipe version: 4
# /usr/xenomai/sbin/version
Xenomai/cobalt v3.0.6 -- #5956064 (2018-03-20 12:13:33 +0100)
Its a very simple API level test.
We create a condition variable and wait for the condition inside a task.
Then, we
13 matches
Mail list logo