All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: "\"Dr. med. Günther Montag\"" <Safari.Doktor@addcom.de>
Cc: alsa-devel@lists.sourceforge.net, hfterm-hackers@lists.sourceforge.net
Subject: Re: ham radio OSS duplex realtime mmap program.
Date: Fri, 26 Sep 2003 15:51:07 +0100	[thread overview]
Message-ID: <3F74525B.4050805@superbug.demon.co.uk> (raw)
In-Reply-To: <200309251628.48034.Safari.Doktor@addcom.de>

Dr. med. Günther Montag wrote:
> Hello
> I work at "hfkernel" by Tom Sailer, a program for pactor/rtty (soundcard ham 
> radio digimodes). It seems complicated, because it uses realtime scheduling, 
> select(), mmap(), and runs in 3 threads. 
> It was made in 1996 for OSS; I am trying to get it running with ALSA. 
> 
> It is unique thing because it can do 
> Pactor without the expensive PTC (something like a radio modem), 
> may be of interest for many hams outside Europe /USA.
> 
> I and friends see messages like
> " 512 fragments passed since last wakeup", in endless loop, leading to 
> crashes, seems to be xruns, not able to ctrl-alt-del, have to switch off 
> machine.
> .
> What do You think, how can ALSA support it, or Do I have to rewrite it for 
> ALSA.
> I tried already with no success to say "Direct" and "non-block" in all 
> combinations to /proc/asound/card0/pcm0p etc... 
> If to rewrite, what function / ioctl matches
> SNDCTL_DSP_GETISPACE...SNDCTL_DSP_GETOSPACE...
> " ioctl(fd_audio, SNDCTL_DSP_GETIPTR, &cinfo) "
> and 
> " ioctl(fd_audio, SNDCTL_DSP_GETOPTR, &cinfo) " ?
> 
> The prog is at https//projects.sourceforge.net/hfterm.
> Here is one of the important functions out of l1/user/oss.c my prog:
> Thanks for Your ideas!
> 
I thought all ham radio was half duplex. i.e. You listen and decode, and 
then transmit if needed. i did not think the listen and transmit worked 
at the same time.
So, in theory, one could have 2 threads.
One receiving audio data, one decoding it, and if the decoder needs to 
transmit anything it stops the receiving thread, and starts a transmit 
thread. There is enough time to close and then open the sound device 
between receive and transmit, so the sound card should never have to 
work in full duplex mode.

Cheers
James




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-09-26 14:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26 11:26 ham radio OSS duplex realtime mmap program Dr. med. Günther Montag
2003-09-26 11:47 ` Paul Davis
2003-09-26 13:52   ` James Courtier-Dutton
2003-09-26 14:33     ` Jaroslav Kysela
2003-09-26 14:50       ` Paul Davis
2003-09-26 16:08         ` Abramo Bagnara
2003-09-26 16:14           ` Paul Davis
2003-09-26 18:36             ` Steve Harris
2003-09-30 11:39             ` Dr. med. Günther Montag
2003-10-03 11:55             ` bugs found in ham program Günther Montag
2003-09-26 14:23 ` ham radio OSS duplex realtime mmap program Jaroslav Kysela
2003-09-26 14:51 ` James Courtier-Dutton [this message]
2003-09-30 11:35   ` [Hfterm-hackers] " Dr. med. Günther Montag

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=3F74525B.4050805@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=Safari.Doktor@addcom.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hfterm-hackers@lists.sourceforge.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.