From: Geoff Patch <grp@cea.com.au>
To: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] semaphore bug??
Date: Tue, 14 Aug 2001 18:55:00 -0000 [thread overview]
Message-ID: <01C12580.59C1CFC0.grp@cea.com.au> (raw)
Hi Folks,
> I don't think you can post to a semaphore from an ISR. You'll
> have to run a DSR and do it there. There's a table in the eCos
> Reference Manual (Device Driver Interface to the Kernel) that
> shows what functions may be called from an ISR. About the only
> thing you can do is ack/mask/unmask interrupts and run a DSR.
This is correct, and I recall other postings to the list about this issue.
It's obviously a fairly common misconception. I come from a pSOS
background, where it is possible to post a semaphore in an ISR, and I also
spent a bad week stumbling over this exact issue .
Could I suggest to the eCos team that an explicit statement of *exactly*
what can and cannot be done in an ISR be inserted into the "eCos Interrupt
Model" section of the Reference manual? I'm sure that this would help a lot
of newbies (like me) retain their sanity. :-)
And while I'm writing, I'd like to say that I think eCos is a great piece
of gear. Hats off to you guys.
Cheers
Geoff
------------------------------
Geoff Patch
Senior Software Engineer
CEA Technologies
Canberra Australia
02-6213 0141
next reply other threads:[~2001-08-14 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 18:55 Geoff Patch [this message]
2001-08-15 0:15 ` Andrew Lunn
2001-08-15 0:24 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 12:21 Warren Jasper
2001-08-14 13:09 ` Grant Edwards
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=01C12580.59C1CFC0.grp@cea.com.au \
--to=grp@cea.com.au \
--cc=ecos-discuss@sources.redhat.com \
/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).