All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Markowski <mm@UDel.Edu>
To: Linux-hams List <linux-hams@vger.kernel.org>
Subject: Re: gMFSK/hamlib/parport
Date: Thu, 19 Feb 2004 11:58:56 -0500	[thread overview]
Message-ID: <20040219165856.GD14329@strauss.udel.edu> (raw)
In-Reply-To: <1077135120.1270.67.camel@oh2bns.ampr.org>

First, thanks to everyone for the very helpful responses.
I'll try them tonight after work and see how it goes.

On Wed 18-Feb-04 at 1512 EST, Tomi Manninen wrote:
> On Wed, 2004-02-18 at 17:27, Mike Markowski wrote:
> 
> > 	Feature request:
> > 	- Are there any patches that allow gMFSK to use
> > 	  a parport for PTT?  If not, I'll be glad to look into
> > 	  possibly re-using the parport code from soundmodem-0.7.
> 
> There is no direct support available. Like Stephane said, hamlib
> can control PTT through the parport.

As far as I know (which isn't much!), there isn't a hamlib config
file.  It seems that rigctl lets you test hamlib but doesn't let
you create a permanent file with settings.  If that's true, I need to
set the PTT device in gMFSK.

So to specify /dev/parport0 as the PTT device, would I in gMSFK
first set Settings/Preferences/Devices/PTT to /dev/parport0
and then enable PTT in the hamlib menu??  I have a feeling I'm
missing something...

	Thanks again,
	Mike  AB3AP

  reply	other threads:[~2004-02-19 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 15:27 gMFSK/hamlib/parport Mike Markowski
2004-02-18 19:15 ` gMFSK/hamlib/parport Wilbert Knol
2004-02-18 19:42 ` gMFSK/hamlib/parport Stephane Fillod
2004-02-18 20:12 ` gMFSK/hamlib/parport Tomi Manninen
2004-02-19 16:58   ` Mike Markowski [this message]
2004-02-19 17:28     ` gMFSK/hamlib/parport Tomi Manninen
2004-02-18 23:32 ` gMFSK/hamlib/parport Alex V Flinsch

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=20040219165856.GD14329@strauss.udel.edu \
    --to=mm@udel.edu \
    --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 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.