All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Mark Spencer <markster@linux-support.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Zaptel Pseudo TDM Bus
Date: Sun, 21 Jul 2002 02:52:37 +0200	[thread overview]
Message-ID: <E17W4xi-00033v-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.33.0207201814170.25617-100000@hoochie.linux-support.net>

On Sunday 21 July 2002 01:25, Mark Spencer wrote:
> 	The primary application we use on this interface (although
> certainly not the only one) is the Asterisk Open Source PBX
> (http://www.asterisk.org) which permits you to build a full featured PBX
> (Private Branch eXchange) or IVR (Interactive Voice Response) server with
> a Linux box.  Using the zaptel infrastructure, Asterisk provides the
> ability to deploy phone service with all your expected call features etc.

But can it give error messages in morse code?

> 	I am very interested in seeking comments both on our driver
> framework, and on how to go about submitting this for kernel inclusion if
> appropriate.

You haven't actually said a lot about the driver framework, judging from my 
quick tour of the code and website.  (Very quick, it's late here.)  Perhaps 
you could wax poetic on this subject?

In my quick tour I was looking for where the saw-off between kernel and
user space is in the source tree, and I began to get the feeling the
whole thing is kernel space, is this correct?

Anyway, this effort is exciting and ambitious.  I *want* to use this, for 
very practical reasons, never mind that it would well turn into yet another 
vibrant embedded application area for Linux.

It strikes me that much of what you're doing qualifies as hard realtime 
programming, particularly where you are doing things like interleaving file 
transmission with realtime voice.  I'm thinking that this may be a good 
chance to give the new Adeos OS-layering technology a test drive, with a view 
to achieving more reliable, lower latency signal processing and equipment 
control.  If things work out, this could qualify as the first genuine 
consumer-oriented hard realtime application for Linux.

-- 
Daniel

  reply	other threads:[~2002-07-21  0:48 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 [this message]
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
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=E17W4xi-00033v-00@starship \
    --to=phillips@arcor.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markster@linux-support.net \
    /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.