Thomas, Brieuc \(GE Healthcare\) wrote:
-Message d'origine-
De : Gilles Chanteperdrix [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 23 avril 2006 14:54
À : Thomas, Brieuc (GE Healthcare)
Cc : xenomai-help@gna.org
Objet : RE: [Xenomai-help] my tick takes a break !!
Philippe Gerum wrote:
If you feel lucky, the 3rd option coming with v2.2 is to get rid of the
UVM and use the new direct call interface now available from user-space
for the VxWorks skin. In such a case, you need 1) the development
trunk/, 2) to load xeno_vxworks, 3) work with the new
Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
If you feel lucky, the 3rd option coming with v2.2 is to get rid of the
UVM and use the new direct call interface now available from user-space
for the VxWorks skin. In such a case, you need 1) the development
trunk/, 2) to load
Philippe Gerum wrote:
Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
If you feel lucky, the 3rd option coming with v2.2 is to get rid of the
UVM and use the new direct call interface now available from user-space
for the VxWorks skin. In such a case, you need 1) the
Hi,I am using kernel 2.6.15.7 and Xenomai 2.1While writing this mail I noticed the probable reason.parameter
#define CONFIG_X86_TSC 1 should be#define CONFIG_XENO_X86_TSC 1
I changed this in src/include/xeno_config.hAfter recompile testsuit worked.I changed the same in
Deepak Joglekar wrote:
Hi,
I am using kernel 2.6.15.7 http://2.6.15.7/ and Xenomai 2.1
While writing this mail I noticed the probable reason.
parameter
#define CONFIG_X86_TSC 1 should be
#define CONFIG_XENO_X86_TSC 1
I changed this in src/include/xeno_config.h
After recompile testsuit
