From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Arif.Abbas@combitechsystems.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Setting tty device interrupt priority, spltty()
Date: Fri, 07 Sep 2001 02:32:00 -0000 [thread overview]
Message-ID: <20010907113243.E7347@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B0379B247@pluto.combitech.se>
> #define SPL_IMP 0x01
> #define SPL_NET 0x02
> #define SPL_CLOCK 0x04
> #define SPL_SOFTNET 0x08
> #define SPL_INTERNAL 0x10
>
> I am not sure on which priority to the tty device (the choices are 0x03 or
> 0x05-0x07 or to simply
> rearrange the prioritys)
> Any suggestions??
The OpenBSD stack uses priorites. The eCos implementation there is no
prioritisation. These are just bits in a flag and are used in
combination of a mutex to provide mutual exclusion. So define you
SPL_TTY as 0x20 and add all the other function/macros as needed.
Andrew
prev parent reply other threads:[~2001-09-07 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 2:20 Arif.Abbas
2001-09-07 2:32 ` Andrew Lunn [this message]
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=20010907113243.E7347@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=Arif.Abbas@combitechsystems.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).