Gilles Chanteperdrix wrote:
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 ski
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)
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 xen
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 ne
Cc : xenomai-help@gna.org
> > Objet : RE: [Xenomai-help] my tick takes a break !!
> >
> > Thomas, Brieuc \(GE Healthcare\) wrote:
> > > I tried it, but there isn't any change !
> > > I've got the same behaviour.
> >
>
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
&
> -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 !!
>
> Thomas, B
Thomas, Brieuc \(GE Healthcare\) wrote:
> I tried it, but there isn't any change !
> I've got the same behaviour.
I could reproduce your bug here. The uvm-timer thread is blocked in W
state, just as if the interrupts were locked.
--
Gilles Chantepe
I tried it, but there isn't any change !
I've got the same behaviour.
Brieuc.
-Message d'origine-
De : Gilles Chanteperdrix [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 21 avril 2006 15:57
À : Thomas, Brieuc (GE Healthcare)
Cc : xenomai-help@gna.org
Objet : RE: [Xenoma
Thomas, Brieuc \(GE Healthcare\) wrote:
> Oh no! Sorry, I mean the real-time tick counter!
Could you try the attached patch ?
--
Gilles Chanteperdrix.
--- include/asm-uvm/system.h~ 2006-04-05 15:08:08.0 +0200
+++ include/asm-uvm/system.h
> > Thomas, Brieuc \(GE Healthcare\) wrote:
> > > Hi every one !
> > >
> > > I really don't understand, my porting of application works very
well
> > > (under vxworks skin), message, semaphore, timer... Except the
task !!
> > > I've got a curious behaviour, when I've got a heavy task, the
kern
Thomas, Brieuc \(GE Healthcare\) wrote:
>
> Thomas, Brieuc \(GE Healthcare\) wrote:
> > Hi every one !
> >
> > I really don't understand, my porting of application works very well
> > (under vxworks skin), message, semaphore, timer... Except the task !!
> > I've got a curious behaviour
Thomas, Brieuc \(GE Healthcare\) wrote:
> Hi every one !
>
> I really don't understand, my porting of application works very well
> (under vxworks skin), message, semaphore, timer... Except the task !!
> I've got a curious behaviour, when I've got a heavy task, the kernel
> tick counter stop
Thomas, Brieuc \(GE Healthcare\) wrote:
> Hi every one !
>
> I really don't understand, my porting of application works very well
> (under vxworks skin), message, semaphore, timer... Except the task !!
> I've got a curious behaviour, when I've got a heavy task, the kernel
> tick counter stop
14 matches
Mail list logo
