Hi,
When I started adding the registry support for pSOS skin I first looked at
the vxworks implementation.
Then I implemented similar functionality in a similar manner for pSOS. So I
make use of the registry code. These changes work fine.
However when adding some more changes where I wanted to
Hi,
It is indeed most likely not a specific Xenomai issue but probably
something linker related.
I found following two patches on the web:
http://lists.busybox.net/pipermail/buildroot/2008-July/021864.html
http://patches.openembedded.org/patch/13645/
The first one is kinda what I was already
Jeff Webb wrote:
On 10/05/2013 01:41 PM, Gilles Chanteperdrix wrote:
at last, here comes Xenomai 2.6.3, available at the usual address:
http://download.gna.org/xenomai/stable/xenomai-2.6.3.tar.bz2
In addition to core bug fixes and improvements, it has the following
more visible changes:
-
I have installed xenomai-2.6.2.1 for linux-3.5.7 under Fedora 13 correctly
and the Xenomai tests like, latency, seem to work properly. I have
written a application and have made it execute in the primary xenomai mode
by rt_task_shadow and the timer mode is set in one shot=aperiodic.
I have put
ali hagigat wrote:
I have installed xenomai-2.6.2.1 for linux-3.5.7 under Fedora 13 correctly
and the Xenomai tests like, latency, seem to work properly. I have
written a application and have made it execute in the primary xenomai mode
by rt_task_shadow and the timer mode is set in one
On 10/09/2013 05:04 AM, Gilles Chanteperdrix wrote:
Jeff Webb wrote:
On 10/05/2013 01:41 PM, Gilles Chanteperdrix wrote:
at last, here comes Xenomai 2.6.3, available at the usual address:
http://download.gna.org/xenomai/stable/xenomai-2.6.3.tar.bz2
In addition to core bug fixes and
/attachments/20131009/83323974/attachment.obj
___
Xenomai mailing list
Xenomai@xenomai.org
http://www.xenomai.org/mailman/listinfo/xenomai
Okay, a bit more information regarding the problem we had for those that
might also run into it...
Apparently the issue was posted a while ago on the Fuse mailing list.
The discussion explains the problem:
http://sourceforge.net/mailarchive/message.php?msg_id=26335934
A bug was filed at glibc:
All,
I'm hoping maybe someone can shed a little more light on the issue we see
occasionally. Occasionally our code using the psos+ skin will fail a
t_suspend(0) with error code -4, which I found to be EINTR and appears to
be set if the XNBREAK flag is set. After digging around in the
On 10/09/2013 06:29 PM, Daniel Merrill wrote:
All,
I'm hoping maybe someone can shed a little more light on the issue we see
occasionally. Occasionally our code using the psos+ skin will fail a
t_suspend(0) with error code -4, which I found to be EINTR and appears to
be set if the XNBREAK
On 10/09/2013 06:29 PM, Daniel Merrill wrote:
All,
I'm hoping maybe someone can shed a little more light on the issue we
see occasionally. Occasionally our code using the psos+ skin will fail
a
t_suspend(0) with error code -4, which I found to be EINTR and appears
to be set if the
On 10/09/2013 06:37 PM, Daniel Merrill wrote:
On 10/09/2013 06:29 PM, Daniel Merrill wrote:
All,
I'm hoping maybe someone can shed a little more light on the issue we
see occasionally. Occasionally our code using the psos+ skin will fail
a
t_suspend(0) with error code -4, which I found to be
On 10/09/2013 06:37 PM, Daniel Merrill wrote:
On 10/09/2013 06:29 PM, Daniel Merrill wrote:
All,
I'm hoping maybe someone can shed a little more light on the issue we
see occasionally. Occasionally our code using the psos+ skin will
fail a
t_suspend(0) with error code -4, which I found
On 10/09/2013 03:46 PM, Petr Cervenka wrote:
Hello everyone.
I have very high latency peaks (~400us) with my configuration when
IPIPE_DEBUG and IPIPE_DEBUG_INTERNAL are !NOT! switched on.
Way to reproduce the issue is to run the latency test (tried with high
priority):
$ sudo
14 matches
Mail list logo
