This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
AW: Some newbie questions
- To: "'Lewin A.R.W. Edwards'" <larwe at larwe dot com>
- Subject: AW: [ECOS] Some newbie questions
- From: "Andreas Hofer" <ho at dsa-ac dot de>
- Date: Tue, 26 Jun 2001 17:37:26 +0200
- Cc: <ecos-discuss at sources dot redhat dot com>
Lewin,
> -----Ursprungliche Nachricht-----
> Von: Lewin A.R.W. Edwards [mailto:larwe@larwe.com]
> Gesendet: Dienstag, 26. Juni 2001 15:06
> An: Andrew Lunn; Andreas Hofer
> Cc: ecos-discuss@sources.redhat.com
> Betreff: Re: [ECOS] Some newbie questions
>
>
>
> >eCos is not a hard real time OS. There is no deadline scheduling, no
> >guarantees. Everything it best effort. You do have priorities per
> >thread, so you can priorities your CAN bus handler above everything
> >else to improve is responce time.
>
> In practice, regardless of the APIs eCos provides, you can
> put whatever
> hardware is connected to the CAN controller on a
> high-priority interrupt
> and disable every other interrupt as soon as you get into that ISR.
>
>
>
But what can I do if I must perform a task "exactly" 123us from now or
if I want to perform periodic tasks with very low jitter? Can I do this
with eCos or do I need a hard realtime OS?
Andreas