public inbox for linux-hams@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tsutsumi Family" <oakie@kamakuranet.ne.jp>
To: 'f6bvp' <f6bvp@free.fr>, 'linux-hams' <linux-hams@vger.kernel.org>
Subject: RE: 300bps soundmodem notes and Broken Pipe
Date: Tue, 7 Dec 2010 10:11:17 +0900	[thread overview]
Message-ID: <8555F01D3F444B67AC183536260E14B0@LIVINGROOM> (raw)
In-Reply-To: <4CFCB9C8.1030408@free.fr>

Hello Bernard,

Thank you for picking up my question about "Broken pipe" issue and sending
your suggestion.

Please be patient for a while as I am not any computer language programmer
at all.

I read the source file of soundmodem and I believe the error message comes
from the second logprintf statement (line 368) in alsaio.c program.

---------------------------alsaio.c--------------------------------
static inline void iotxstart(struct audioio_unix *audioio)
{      
        int err;
       
        if (snd_pcm_prepare(audioio->playback_handle) < 0) {
                logprintf(MLOG_ERROR, "Error preparing tx.\n");
        }
        err = snd_pcm_start(audioio->playback_handle);
        if (err < 0)
                logprintf(MLOG_ERROR, "snd_pcm_start in iotxstart: %s",
snd_strerror(err));
}
-------------------------------------------------------------------

Can you explain me the following questions concerning your suggestion?

1. Are you suggesting adding additional three lines in alsaio.c program?
If yes, which exact lines should I add?

2. What is the purpose and expected result of signal (SIGPIPE, SIG_IGN)
addition?

I am waiting your response soon.

Regards,

take

de JA5AEA
-----Original Message-----
From: f6bvp [mailto:f6bvp@free.fr] 
Sent: Monday, December 06, 2010 7:24 PM
To: oakie@kamakuranet.ne.jp; linux-hams
Subject: RE: 300bps soundmodem notes and Broken Pipe

Hi,

You could try adding this in soundmodem :

#include<signal.h>
...
main()
...
...
signal (SIGPIPE, SIG_IGN);

73 de Bernard, f6bvp


-----Original Message-----
John,

Excellent note to the soundmodem beginners.

Concerning the soundmodem program, I often experience "broken pipe" errors
in high speed transmission setting with slow CPU machines and it looks like
one of the popular questions unexplained.

Can I have suggestion from the experienced linux-hams the proper ways to
fix?

Regards,

take

de JA5AEA


  reply	other threads:[~2010-12-07  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 10:24 300bps soundmodem notes and Broken Pipe f6bvp
2010-12-07  1:11 ` Tsutsumi Family [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-09 20:14 f6bvp
2011-03-02  6:22 ` Tsutsumi Family
2010-12-03  3:33 300bps soundmodem notes John Goerzen
2010-12-03 15:00 ` 300bps soundmodem notes and Broken Pipe Tsutsumi Family

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=8555F01D3F444B67AC183536260E14B0@LIVINGROOM \
    --to=oakie@kamakuranet.ne.jp \
    --cc=f6bvp@free.fr \
    --cc=linux-hams@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