public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Tony Ko" <nhko@gctsemi.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] question about stack assign for interrupt service routine.
Date: Wed, 25 Jul 2001 06:09:00 -0000	[thread overview]
Message-ID: <9860C773D04D834D83FD6FAD00A61E930F2040@gctsemi.gctsemi.com> (raw)

hi.
i understand new stack is assigned per thread.
then, what about interrupt?
is new stack  assigned per interrupt?

thanks in advance.

tony.


             reply	other threads:[~2001-07-25  6:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  6:09 Tony Ko [this message]
2001-07-25  7:16 ` [ECOS] Question about Hello World eCos example Andre Sebastien
2001-07-25  7:38   ` Robin Farine
2001-07-25  8:14     ` Andre Sebastien
2001-07-25  8:45       ` Robin Farine
2001-07-25  9:11   ` David Airlie
2001-07-25 11:26 ` [ECOS] question about stack assign for interrupt service routine Jonathan Larmour
2001-07-25 13:59   ` [ECOS] question about GCC for Arm Installation Grant Whitacre
2001-07-25 14:53     ` Jonathan Larmour

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=9860C773D04D834D83FD6FAD00A61E930F2040@gctsemi.gctsemi.com \
    --to=nhko@gctsemi.com \
    --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).