From: Karim Yaghmour <karim@opersys.com>
To: Paul Zimmerman <Paul_Zimmerman@inSilicon.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Adeos nanokernel for Linux kernel
Date: Wed, 05 Jun 2002 15:11:23 -0400 [thread overview]
Message-ID: <3CFE625B.AB445C6C@opersys.com> (raw)
In-Reply-To: <7FD8B823E5024E44B027221DEB34C087536524@scl-exch.phoenix.com>
Paul Zimmerman wrote:
> What if I'm unfortunate enough to have my sound card share an interrupt
> with my IDE controller? Won't my realtime audio player still be at the
> mercy of my non-realtime Linux IDE driver? Or does Adeos have a way to
> handle that?
That's an interesting case. There is nothing against the RTOS and
Linux both asking the ipipe to signal them if this interrupt occurs.
The RTOS would get it first, decide whether its the sound card and do
whatever it needs to do with it. Whether it needs it or not, it doesn't
terminate the interrupt so the interrupts makes its way through the ipipe
and ends up somewhere afterwards in Linux's hands which can then deal
with it as it sees fit.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-06-05 19:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 19:01 [ANNOUNCE] Adeos nanokernel for Linux kernel Paul Zimmerman
2002-06-05 19:11 ` Karim Yaghmour [this message]
2002-06-05 20:17 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 9:24 Martin.Knoblauch
2002-06-03 8:35 Karim Yaghmour
2002-06-03 8:46 ` Erik Andersen
2002-06-03 8:56 ` Alessandro Rubini
2002-06-03 9:14 ` Karim Yaghmour
2002-06-03 9:52 ` Erik Andersen
2002-06-03 10:05 ` Alessandro Rubini
2002-06-03 10:12 ` Karim Yaghmour
2002-06-03 10:33 ` Erik Andersen
2002-06-03 10:38 ` Karim Yaghmour
2002-06-03 11:05 ` Daniel Phillips
2002-06-03 9:26 ` Daniel Phillips
2002-06-04 19:29 ` Oliver Xymoron
2002-06-05 2:20 ` Daniel Phillips
2002-06-05 2:40 ` Oliver Xymoron
2002-06-05 2:57 ` Daniel Phillips
2002-06-05 13:51 ` Oliver Xymoron
2002-06-05 14:25 ` Daniel Phillips
2002-06-05 15:37 ` Oliver Xymoron
2002-06-05 17:32 ` Daniel Phillips
2002-06-05 18:06 ` Mark Mielke
2002-06-05 18:26 ` Daniel Phillips
2002-06-05 19:13 ` Oliver Xymoron
2002-06-05 19:40 ` Daniel Phillips
2002-06-05 20:51 ` Mark Mielke
2002-06-05 21:45 ` Daniel Phillips
2002-06-05 21:22 ` Oliver Xymoron
2002-06-05 21:55 ` Daniel Phillips
2002-06-06 8:52 ` Peter Wächtler
2002-06-06 10:58 ` Daniel Phillips
2002-06-06 14:03 ` Peter Wächtler
2002-06-06 16:53 ` Daniel Phillips
2002-06-05 20:48 ` Mark Mielke
2002-06-06 8:34 ` Peter Wächtler
2002-06-08 13:50 ` john slee
2002-06-08 13:59 ` Thunder from the hill
2002-06-06 21:21 ` Pavel Machek
2002-06-07 1:35 ` Mark Mielke
2002-06-07 2:42 ` Daniel Phillips
2002-06-07 2:48 ` Mark Mielke
2002-06-07 10:32 ` Daniel Phillips
2002-06-07 21:35 ` Pavel Machek
2002-06-05 9:41 ` Ingo Oeser
2002-06-05 18:20 ` Karim Yaghmour
2002-06-05 3:56 ` J Sloan
2002-06-05 4:08 ` Daniel Phillips
2002-06-05 7:28 ` Eric W. Biederman
2002-06-05 11:15 ` Peter Wächtler
2002-06-05 12:56 ` Daniel Phillips
2002-06-05 11:11 ` Peter Wächtler
2002-06-05 16:55 ` Rob Landley
2002-06-04 16:10 ` Pavel Machek
2002-06-04 19:59 ` Karim Yaghmour
2002-06-04 21:53 ` Karim Yaghmour
2002-06-04 23:06 ` Alan Cox
2002-06-05 4:00 ` Daniel Phillips
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=3CFE625B.AB445C6C@opersys.com \
--to=karim@opersys.com \
--cc=Paul_Zimmerman@inSilicon.com \
--cc=linux-kernel@vger.kernel.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