On 6/1/20 12:23 PM, Meng, Fino via Xenomai wrote:
Sent: Monday, June 1, 2020 4:09 PM
Hi all!
I have a PCIe device in x86 motherboard that generate periodic MSI-X interrupts
and I would like to handle them in the head
stage, how it can be done?
Thank you! Appreciate any help!
Best,
On 02.06.20 09:37, Alexander Frolov via Xenomai wrote:
> Hi all!
>
> I've encountered with the following ipipe error message. What can it be?
> Thank you!
>
> Best,
> Alex
>
>
> [ 2275.770959] I-pipe: Detected stalled head domain, probably caused by
> a bug.
> A
On 31.05.20 05:29, Greg Gallagher via Xenomai wrote:
> From: Joshua Karch
>
> Signed-off-by: Joshua Karch
> Signed-off-by: Greg Gallagher
> ---
> kernel/drivers/gpio/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/drivers/gpio/Kconfig
On 01.06.20 15:51, Greg Gallagher via Xenomai wrote:
> I'm not sure if the rpi4 is in mainline yet but you may have more
> success trying this with the mainline kernel
>
The RPi4 is still far aways from mainline, unfortunately. The usual
downstream mess.
Jan
--
Siemens AG, Corporate
On 02.06.20 08:40, Alexander Frolov via Xenomai wrote:
>
>
> On 6/1/20 12:23 PM, Meng, Fino via Xenomai wrote:
>>
>>> Sent: Monday, June 1, 2020 4:09 PM
>>>
>>> Hi all!
>>>
>>> I have a PCIe device in x86 motherboard that generate periodic MSI-X
>>> interrupts and I would like to handle them in
Hi all!
I've encountered with the following ipipe error message. What can it be?
Thank you!
Best,
Alex
[ 2275.770959] I-pipe: Detected stalled head domain, probably caused by
a bug.
A critical section may have been left unterminated.
[ 2275.770965] CPU: 2 PID: 0
On 2020年06月02日 15:49, Jan Kiszka wrote:
On 01.06.20 15:51, Greg Gallagher via Xenomai wrote:
I'm not sure if the rpi4 is in mainline yet but you may have more
success trying this with the mainline kernel
The RPi4 is still far aways from mainline, unfortunately. The usual
downstream mess.
On 02.06.20 10:51, chensong wrote:
>
>
> On 2020年06月02日 15:49, Jan Kiszka wrote:
>> On 01.06.20 15:51, Greg Gallagher via Xenomai wrote:
>>> I'm not sure if the rpi4 is in mainline yet but you may have more
>>> success trying this with the mainline kernel
>>>
>>
>> The RPi4 is still far aways
On 2020年06月02日 17:08, Jan Kiszka wrote:
On 02.06.20 10:51, chensong wrote:
On 2020年06月02日 15:49, Jan Kiszka wrote:
On 01.06.20 15:51, Greg Gallagher via Xenomai wrote:
I'm not sure if the rpi4 is in mainline yet but you may have more
success trying this with the mainline kernel
The
- VAT IT 03354081204
>
> __
>
> *The information contained in this e-mail and any attachments is
> confidential and may also be privileged. If you have received the
> e-mail and any attachments by mistake, please inform us immediately,
> destroy them without storing or copying them on any medium, and do not
> disclose or use the contents for any purpose.*
> *Although our systems implement reasonable precautions against viruses and
> other threats, we cannot accept responsibility for any loss or damage
> arising from managing the contents of this e-mail. *
>
> *P* *Please consider the environment before printing this e-mail*
>
Are you still seeing the issue? I finally looked over the diff, still
looking at a few things but it looks good.
-- next part --
A non-text attachment was scrubbed...
Name: noname
Type: image/jpeg
Size: 19872 bytes
Desc: not available
URL:
<http://xenomai.org/pipermail/xenomai/attachments/20200602/99d135b6/attachment.jpe>
Dear all,
I tried to have an example using rtdm_task_init with Xenomai 3.0.7. The example
is tis one:
—
#include
static int periode_us = 1000;
static int a, ret;
module_param(periode_us, int, 0644);
rtdm_task_t task;
void task_ultrason(void *arg){
a=1;
rtdm_printk(KERN_INFO
11 matches
Mail list logo
