All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Mark Spencer <markster@linux-support.net>
Cc: Daniel Phillips <phillips@arcor.de>, linux-kernel@vger.kernel.org
Subject: Re: Zaptel Pseudo TDM Bus
Date: Sun, 21 Jul 2002 17:39:29 -0400	[thread overview]
Message-ID: <3D3B2A11.5DB3C08B@opersys.com> (raw)
In-Reply-To: Pine.LNX.4.33.0207211551350.25617-100000@hoochie.linux-support.net


Mark Spencer wrote:
> > That said, Adeos does offer what appears to be an very efficient model for
> > handling interrupts.  (Caveat: I haven't tried it myself yet, much less
> > measured it, just eyeballed the code)  You can load a module directly into
> > the interrupt pipeline and bypass all of Linux's interrupt machinery, even
> > bypass cli (it just sets a flag in Adeos).
> 
> If someone involved with, or familiar with, this project would care to
> contact me, I'd be happy to talk about RT enabling zaptel / asterisk.

Right here :)

Any driver that needs direct access to the interrupts can use Adeos' interrupt
pipeline. Your driver's low-level operations should be fairly easy to port to
Adeos.

Since Adeos' release, such porting of code has actually been successfully
done a couple of times already. Apart from Philippe's porting of the Xenomai
interface, here's an interesting tidbit that appeared on the Adeos mailing
list:
> We managed to get a proprietary (sorry nobody's perfect) RT nanokernel
> working with ADEOS. Thus we have two different OSes working at the same
> time on the same computer thanks to ADEOS. 

And yet another:
> I explored yesterday the Adeos nanokernel and was surprised by the
> possibilities and also the stability!
> 
> I tested for example multiple domains having different priorities and
> installing handlers on the same interrupt which works exactly is it is
> described.
> 
> I also tested snooping other interrupts (mouse/keyboard/ide0/ethernet)
> then the timer example provided in the package. (which works ofcourse
> also great)

Feel free to post any questions to Adeos' mailing list. It's been quite
active lately and I'm sure your application will interest others.

Adeos' web site is at:
http://www.freesoftware.fsf.org/adeos/

If you're looking for an introduction to Adeos' functionality have a look
at the original LKML announcement:
http://lwn.net/Articles/1743/

Best regards,

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

  reply	other threads:[~2002-07-21 21:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-20 23:25 Zaptel Pseudo TDM Bus Mark Spencer
2002-07-21  0:52 ` Daniel Phillips
2002-07-21 18:59   ` Mark Spencer
2002-07-21 20:46     ` Daniel Phillips
2002-07-21 21:00       ` Mark Spencer
2002-07-21 21:39         ` Karim Yaghmour [this message]
2002-07-21 23:09         ` Daniel Phillips
2002-07-21  1:27 ` Daniel Phillips
2002-07-21 19:01   ` Mark Spencer
2002-07-21 20:04     ` Daniel Phillips
2002-07-21 20:49       ` Mark Spencer
2002-07-21 13:14 ` Francois Romieu

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=3D3B2A11.5DB3C08B@opersys.com \
    --to=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markster@linux-support.net \
    --cc=phillips@arcor.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.