Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
When configuring kernel (4.19.144 arm) through menuconfig, I get the
following warning:
[*] Xenomai/cobalt --->
*** WARNING! Page migration (CONFIG_MIGRATION) may increase ***
*** latency. ***
But I'm not able
When configuring kernel (4.19.144 arm) through menuconfig, I get the
following warning:
[*] Xenomai/cobalt --->
*** WARNING! Page migration (CONFIG_MIGRATION) may increase ***
*** latency. ***
But I'm not able to disable it:
Memory Management options --->
-*- Page migration
Is it po
what is going on in the system.
Song
On 2021/3/1 上午6:26, Gabriel Dinse via Xenomai wrote:
Hello,
I'm doing a comparison of interrupt handling on Xenomai using a
raspberry pi 3-b in 2 situations:
1- No stress
2- Running stress-ng on terminal: $ nice -19 stress-ng -c 4
--metrics --time
Hello,
I'm doing a comparison of interrupt handling on Xenomai using a
raspberry pi 3-b in 2 situations:
1- No stress
2- Running stress-ng on terminal: $ nice -19 stress-ng -c 4 --metrics
--timeout 120s&
What I do is to create a periodic task (priority 50) that runs every
500us activating gp
On Sun, Feb 28, 2021 at 8:08 am, Greg Gallagher
wrote:
On Sun, Feb 28, 2021 at 7:18 AM Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
Hello,
I currently have a loop rt_task for reading interrupts on a GPIO
pin of
my raspberry pi.
I'm using:
ret = read(
Hello,
I currently have a loop rt_task for reading interrupts on a GPIO pin of
my raspberry pi.
I'm using:
ret = read(pin, &value, sizeof(value));
but I don't want it to block forever, because my task should exit when
there are not more interrupts to read. Can I use "select" for
introducing
ailto:g...@embeddedgreg.com>>
wrote:
On Mon, Feb 22, 2021 at 3:19 PM Gabriel Dinse
<mailto:gabriel_di...@hotmail.com>> wrote:
On Mon, Feb 22, 2021 at 9:12 am, Greg Gallagher
mailto:g...@embeddedgreg.com>>
wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse via
Xeno
ailto:g...@embeddedgreg.com>>
wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
> This is a 32-bit build running on the rpi3?
Yes, it is
> I have some ipipe fixes coming, but I don't think
these are ipipe
related.
mailto:gabriel_di...@hotmail.com>> wrote:
On Mon, Feb 22, 2021 at 9:12 am, Greg Gallagher
mailto:g...@embeddedgreg.com>> wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
> This is a 32-bit build running on the rpi3?
6 pm, Greg Gallagher
mailto:g...@embeddedgreg.com>> wrote:
On Mon, Feb 22, 2021 at 3:19 PM Gabriel Dinse
mailto:gabriel_di...@hotmail.com>>
wrote:
On Mon, Feb 22, 2021 at 9:12 am, Greg Gallagher
mailto:g...@embeddedgreg.com>> wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse
2 am, Greg Gallagher
mailto:g...@embeddedgreg.com>> wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
> This is a 32-bit build running on the rpi3?
Yes, it is
> I have some ipipe fixes coming, but I don't think these
are ipipe
rel
abriel Dinse
mailto:gabriel_di...@hotmail.com>>
wrote:
On Mon, Feb 22, 2021 at 9:12 am, Greg Gallagher
mailto:g...@embeddedgreg.com>> wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
> This is a 32-bit build running on
On Mon, Feb 22, 2021 at 5:26 pm, Greg Gallagher
wrote:
On Mon, Feb 22, 2021 at 3:19 PM Gabriel Dinse
mailto:gabriel_di...@hotmail.com>> wrote:
On Mon, Feb 22, 2021 at 9:12 am, Greg Gallagher
mailto:g...@embeddedgreg.com>> wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabri
On Mon, Feb 22, 2021 at 9:12 am, Greg Gallagher
wrote:
On Mon, Feb 22, 2021 at 5:15 AM Gabriel Dinse via Xenomai
mailto:xenomai@xenomai.org>> wrote:
> This is a 32-bit build running on the rpi3?
Yes, it is
> I have some ipipe fixes coming, but I don't think these a
> This is a 32-bit build running on the rpi3?
Yes, it is
> I have some ipipe fixes coming, but I don't think these are ipipe
related.
> Can you show how you patched and built your kernel? I'll try to
reproduce
> on my end. What compiler are you using?
For patching the kernel, I did:
xenomai-
Hello,
I'm currently compiling linux 5.4.93 patched with xenomai 3.1,
using ipipe 5.4.93 for arm. The system is intended to run on a raspberry
pi 3 b, but I'm getting the following errors related to incompatible
pointer type:
CALLscripts/atomic/check-atomics.sh
CALLscripts/checksyscalls
Hello,
You are right, I am using this one: https://github.com/raspberrypi/tools, but I
can’t manage how to check its glibc version
(arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/)
I am trying to use mainline Kernel. I think xenomai has a fork for RPI kernel
4.1 but it is not up to date, right? Also, the right paper is
http://kth.diva-portal.org/smash/get/diva2:1251188/FULLTEXT01.pdf, not the
other one I sent. The author managed to use kernel 4.9.51 disabling support for
Hello,
Actually I’m using kernel 4.9.51. Im using this guide and another paper:
https://kth.diva-portal.org/smash/get/diva2:1381368/FULLTEXT01.pdf (based on
the github guide) as a guideline. The paper uses 4.9.51
Best regards,
Gabriel Dinse
Hello,
I’m not used to use email this way, but answering your question on the hidden
email LOL,
I’m compiling for Raspberry PI 1 B on the environment I showed, following this
guide:
https://github.com/harcokuppens/xenomai3_rpi_gpio/blob/master/install/install_xenomai-3-3.0.5_on_rpi1__ipipe_git.
Hello, I’m getting the following error when doing:
~/xenomai-3/build$ make install
[… MORE OUTPUT ...]
make[3]: Entering directory '/home/gabriel/xenomai-3/build/lib/cobalt'
CC libcobalt_la-rtdm.lo
../../../lib/cobalt/rtdm.c: In function ‘__cobalt___open_2’:
../../../lib/cobalt/rtdm.c:104:
21 matches
Mail list logo
