public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Yi Tang" <yitang@itee.uq.edu.au>
To: "eCos-discuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] multiple alarms to same clock
Date: Wed, 19 Sep 2007 12:53:00 -0000	[thread overview]
Message-ID: <002501c7fabb$fb8b7ec0$82406682@itee.uq.edu.au> (raw)

Hi All,

I have writen an application for ecos alarm. In my application, I found that 
if two or more alarms connected to the same clock and they are triggered at 
the same time, kernel will only react to one alarm and neglect another. That 
caused some realtime behavior in my application be missed out. My alarms are 
connected to real-time-clock. And I have tried both the sorted and unsorted 
list. Wondering if that's a bug for kernel or there can be something wrong 
with my application code?

Regards,
Yi Tang
ITEE School, University of Queensland 



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2007-09-19 12:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002501c7fabb$fb8b7ec0$82406682@itee.uq.edu.au' \
    --to=yitang@itee.uq.edu.au \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).