[Xenomai] testsuite/smokey/dlopen fails to build when building out of tree

git checkout stable-3.0.x scripts/bootstrap mkdir -p ../xenomai-3-build && cd ../xenomai-3-build ../xenomai-3/configure --with-core=cobalt --enable-pshared --host=arm-linux-gnueabihf --build=arm CFLAGS="-march=armv7-a -mfpu=vfp3" --enable-dlopen-libs make V=1 will eventually result in

[Xenomai] Low latency under stress, otherwise high latency

Hi folks, after installing Xenomai 3.0.5/kernel 4.9.38 following [1] on our Dell Precision 5820 machine (Intel Xeon W-2145), there are high latencies when the system is at rest. When starting a stress test via `stress -v -c 8 -i 10 -d 8`, the latency goes down (see terminal output below).

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

As Philippe mentioned, they are some missing pieces that need to be added to the ipipe. The link Philippe provided will give you guidance on how to make those changes to your custom kernel. The other option is you could use the ipipe-arm tree and the mainline kernel. Also, unrelated, the gpios

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

Xenomai 3.0.6, and ipipe-core-4.9.51-arm-3, patched on sunxi 4.11.2 kernel (with BeagleBone patches applied too). Same situation with this kernel -> https://github.com/beagleboard/linux/tree/4.9-xenomai Just as Giulio wrote, GPIO is configured with: echo 60 > /sys/class/gpio/export echo both >

Re: [Xenomai] [PATCH v2] lib/boilerplate: Prevent migration to secondary mode for __printout

On 02/26/2018 06:45 PM, Jan Kiszka wrote: > From: Wolfgang Hartmann > > Use the __RT versions of the stdio function calls to avoid migration to > secondary mode. In case of ___panic, flush the printer before exiting to > avoid losing messages. > > Signed-off-by:

[Xenomai-git] Wolfgang Hartmann : lib/boilerplate: Prevent migration to secondary mode for __printout

Module: xenomai-3 Branch: stable-3.0.x Commit: 9da7bde25afaf5d6fb7f91a44bc2e96019cd4acb URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=9da7bde25afaf5d6fb7f91a44bc2e96019cd4acb Author: Wolfgang Hartmann Date: Mon Feb 26 18:45:00 2018 +0100

[Xenomai-git] Wolfgang Hartmann : lib/boilerplate: Prevent migration to secondary mode for __printout

Module: xenomai-3 Branch: next Commit: 55736da6c71877b1347d465f2790f7bbe2155939 URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=55736da6c71877b1347d465f2790f7bbe2155939 Author: Wolfgang Hartmann Date: Mon Feb 26 18:45:00 2018 +0100 lib/boilerplate:

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

On 02/26/2018 02:46 PM, branislav.sa...@automatika.imp.bg.ac.rs wrote: > Hello, > > I have a problem with new I-pipe patch, which was not existing with legacy > patch on 3.14 kernel, on BeagleBone platform. > > When GPIO pin is configured as input with edge interrupt enable, on IRQ > occurrence

[Xenomai] [PATCH v2] lib/boilerplate: Prevent migration to secondary mode for __printout

From: Wolfgang Hartmann Use the __RT versions of the stdio function calls to avoid migration to secondary mode. In case of ___panic, flush the printer before exiting to avoid losing messages. Signed-off-by: Wolfgang Hartmann

Re: [Xenomai] [RTDM] Converting existing Linux char driver to rtdm driver

You'd have to decide what functionality you want with respect to rt and non rt for your driver. What's confusing about the context? The gpio driver is pretty up to date, you can look at it for some guidance. Unfortunately there isn't a lot of documentation at the moment, so your best bet is to

Re: [Xenomai] [RTDM] Converting existing Linux char driver to rtdm driver

Dear Jan, This thread is about porting a normal misc char driver to rtdm model. Anyways I got some clue by looking into rtdmtest driver. But what is confusing to me is the rtdm context_ part and the rt, nrt part. How can I map this eith my exusting driver? Can I leave the context part NULL and

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

Is it possible to try this with the latest Xenomai stable branch? There have been a good amount of fixes and changes in the branch since 3.0.5. git clone git://git.xenomai.org/xenomai-3.git git checkout stable-3.0.x Then you can follow the steps as you did for 3.0.5 to patch the kernel. Is this

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

Yes correct, we have Xenomai installed and tried to use a pin through the linux sysfs interface. Xenomai was not using that same pin (or any other GPIO pins, for what matters). Thanks, Giulio From: Greg Gallagher Sent: 26 February

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

In this case you have Xenomai installed and are using the GPIO in a non rt situation? On Zynq I can use both the RTDM gpios and the sysfs gpios (non rt) at the same time as long as it's not the same pin. I will look into this this week, I have RPI stuff on the go as well so patience is

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

We have a similar issue on Linux 4.4.87 and 4.4.113, with xenomai 3.0.5: https://github.com/RobertCNelson/ti-linux-kernel-dev/issues/16 (comes with code to reproduce issue). Best, Giulio From: Xenomai on behalf of Greg

Re: [Xenomai] interrupt on edge problem, unexpected IRQ trap

Can you provide what version of Xenomai you are using and what ipipe patch you are using? It also may be helpful if you could provide some sort of sample code that reproduces the problem. -Greg On Mon, Feb 26, 2018 at 8:46 AM, wrote: > Hello, > > I have

[Xenomai] interrupt on edge problem, unexpected IRQ trap

Hello, I have a problem with new I-pipe patch, which was not existing with legacy patch on 3.14 kernel, on BeagleBone platform. When GPIO pin is configured as input with edge interrupt enable, on IRQ occurrence the following message appears: [ 303.331386] irq 88, desc: dc1be400, depth: 0,

Re: [Xenomai] [RTDM/rt-serial] How to verify 16550A on Ubuntu desktop

+1 for that solution, this link helped me when i was trying to unbind the imx uart driver. https://lwn.net/Articles/143397/ On Mon, Feb 26, 2018 at 8:24 AM, Johann Obermayr wrote: > Hi, > > Take a look into the file /proc/tty/driver/serial > Here you see all found

Re: [Xenomai] [RTDM] Converting existing Linux char driver to rtdm driver

On 2018-02-26 12:26, Pintu Kumar wrote: > Hi, > > I have a sample linux char driver which I am registering using normal > misc_register/deregister function. > In this driver, I have used, open, read, write, ioctl, release system calls. > > Now I wanted to convert this driver to RTDM interface

Re: [Xenomai] [RTDM/rt-serial] How to verify 16550A on Ubuntu desktop

Hi, Take a look into the file /proc/tty/driver/serial Here you see all found uart and used linux driver and uart parameter (port, irq,..) With follow function you can unbind the linux driver static int uart_unbind(int ttynr) { char dev[64]; int fd; struct serial_struct

[Xenomai] [RTDM] Converting existing Linux char driver to rtdm driver

Hi, I have a sample linux char driver which I am registering using normal misc_register/deregister function. In this driver, I have used, open, read, write, ioctl, release system calls. Now I wanted to convert this driver to RTDM interface and compare it. Later I wanted to add some more use

[Xenomai] [RTDM/rt-serial] How to verify 16550A on Ubuntu desktop

Hi, I have enabled RTDM serial driver 16550A in kernel and I am using it with x86-64 Ubuntu 16.04 desktop. CONFIG_XENO_DRIVERS_16550A=y CONFIG_XENO_DRIVERS_16550A_PIO=y Now I wanted to verify this driver using a sample application such as : cross-link But, when I check, the driver is not