On 28/02/06, Jan Kiszka [EMAIL PROTECTED] wrote:
Jim Cromie wrote:LDdrivers/xenomai/16550A/built-in.oCC [M]drivers/xenomai/16550A/16550A.o /mnt/dilbert/jimc/dilbert/lxbuild/linux-2.6.15.1-ipipe-121/drivers/xenomai/16550A/16550A.c:
In function ?rt_16550_interrupt?:
Dmitry Adamushko wrote:
Hello,
Linux'es enable/disable_irq() should not be called from the primary domain.
Applied, thanks.
In short, they use a normal linux spinlock + irq are off only for the
Linux domain;
the precise description is available here :
Steven Seeger wrote:
I do not recall having this problem with fusion, but I'll take your word on
it. I don't have time to go back and check. :)
Purging the overrun count when rt_task_wait_period() is called may work but
not for all conditions. For example, say I am monitoring a patient's
[EMAIL PROTECTED] wrote:
Dear Gilles,
perhaps I should have mentioned in my earlier postings that I am using a
PowerPC platform. I hope this does not nullify your prior analyses.
As the following output shows, my timer is running in onshot mode :
~ # cat /proc/xenomai/timer
[EMAIL PROTECTED] wrote:
Philippe Gerum wrote :
I've run the satch example successfully on an Icecube board
here using -rc2.
What's the status of this issue on your side? Was it a timer
configuration issue as suspected by Gilles?
Status is unchanged. I still try to debugg satch with
On 01/03/06, Philippe Gerum [EMAIL PROTECTED] wrote:
The other option I've described fordealing with overruns in rt_task_wait_period would be as follows:
- save the count of overruns- clear the count of overruns/* i.e. purge */- return both the saved count and -ETIMEDOUT to the user.This way,
Dmitry Adamushko wrote:
On 01/03/06, *Philippe Gerum* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
The other option I've described for
dealing with overruns in rt_task_wait_period would be as follows:
- save the count of overruns
- clear the count of overruns /*
Philippe Gerum wrote:
[EMAIL PROTECTED] wrote:
Philippe Gerum wrote :
I've run the satch example successfully on an Icecube board
here using -rc2.
What's the status of this issue on your side? Was it a timer
configuration issue as suspected by Gilles?
Status is
Jan,
We don't know how to compile the VxWork skin of xenomai to support C++
code. We need some help!
Thanks,
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 3:58 AM
To: Wu, John
Cc: xenomai-core@gna.org; Chau, Ngaiman
Wu, John wrote:
Jan,
We don't know how to compile the VxWork skin of xenomai to support C++
code. We need some help!
Unless we are missing something, there is no need to compile vxworks
skin in a special way in order to support C++ code.
Xenomai vxworks skin functions are declared
On 01/03/06, Philippe Gerum [EMAIL PROTECTED] wrote:
Dmitry Adamushko wrote: On 01/03/06, *Philippe Gerum* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
The other option I've described for dealing with overruns in rt_task_wait_period would be as follows: - save the count of overruns - clear
Wu, John wrote:
Jan,
We don't know how to compile the VxWork skin of xenomai to support C++
code. We need some help!
Sorry, I still don't get your problem. Regarding compiling and linking,
there should be nothing special about C++ vs. C and Xenomai's VxWorks
skin (bugs aside). It's like
12 matches
Mail list logo
