From: chuck gelm <chuck@gelm.net>
To: Matti Aarnio <matti.aarnio@zmailer.org>,
Dave Platt <dplatt@radagast.org>
Cc: Linux-hams List <linux-hams@vger.kernel.org>
Subject: ? software requirements: MT63lx version 0.5
Date: Thu, 15 Jul 2004 09:42:04 -0400 [thread overview]
Message-ID: <40F689AC.8020606@gelm.net> (raw)
In-Reply-To: <20040715074739.GO1486@mea-ext.zmailer.org>
MT63lx software requirements: ?
Matti Aarnio wrote:
> On Wed, Jul 14, 2004 at 11:23:55PM -0400, chuck gelm wrote:
>
>>>On Mon, Jul 12, 2004 at 11:05:10PM -0400, chuck gelm wrote:
>>>
>>>>I have seen mention of this "MT63" every few weeks or months here on the
>>>>linux-hams mail list. Where can I obtain a description of what MT63 is
>>>>and what hardware it requires?
I meant to ask about the hardware requirements of the sound card
(computer interface) rather than the electrical requirements of the
SSB transceiver audio in/out.
Sorry.
gMFSK requires, seemingly, a generic sound card.
>>>
>>>>Chuck nc8q
>>
>>>73 de Matti, OH2MQK
>>
>>Thanks, Matti:
>>
> I do get a feeling, that you need some Elmer guidance from
> people who have done it already, preferrably at your nearest
> hamradio club. With these interface issues it really doesn't
> matter, if the computer runs Linux or Windows. Same interface
> for serial port/audio card/radio will work.
>
>
>> Thus,
>>I am still uncertain if I have or will obtain the necessary hardware.
Thanks. I think that I have the necessary hardware to interface
from the sound card to the SSB transceiver.
Now about the software requirements...
>> Also,
>>I didn't see any mention of kernel version or CPU speed or tools or...
> The 'mt63' standalone modem uses slightly less CPU power, than
> the one in gmfsk -- text mode user interface is less CPU intensive,
>
> See this page, and links onwards from there:
> http://freshmeat.net/projects/gmfsk/
Now I am asking for the software requirements of 'MT63'.
I am aware of the hardware requirements between the computer sound
card and the radio. I believe that I do not need additional help
from the 'line in' and speaker output <> SSB transceiver, as my
existing interface should work.
What I am looking for now is the software requirements of the
'standalone' application 'MT63'.
So far, Matti and Dave have responded and they both mentioned
gMFSK. So, I looked at gMFSK. Here is what I found out about
gMSFK and this is along the same line as what I am looking for
with MT63.
gMSFK:
It is alpha code (still in development)
It requires X11.
It requires Gnome libraries,
but does not require the Gnome desktop environment.
It is intended for Advanced End Users
It is licensed under OSI:GNU:GPL
It works with POSIX *nix and POSIX Linux.
It requires FFTW v2.1.5 which is a developers' tool.
(download link provided at freshmeat.org)
It requires 'libgnome' and here is where things get crazy.
From this point things start to sound like the Abbott and Costello
"Who's on first?" routine.
The description of 'libgnome' is
"GNOME 2 is a new desktop environment which is an extension to GNOME 1"
(So, if 'libgnome' == 'GNOME 2'; why is it called 'libgnome'?)
Does 'GNOME 2' contain 'GNOME 1' ?
'GNOME 2' (? a.k.a. libgnome-2.0) is available for download.
(links were provided from the freshmeat link sited by Matti.)
How does one obtain 'Gnome 1' ?
GNOME 2 requires 'GTK 2' and 'Object Activation Framework'
How does one acquire 'GTK 2' ?
How does one acquire 'Object Activation Framework' ?
So, I was looking for an answer somewhat along this theme:
gMFSK requires:
X11
Gnome liraries
FFTW v2.1.5
libgnome
Gnome 2
Gnome 1
GTK 2
Object Activation Framework
What software does MT63lx version 0.5 require ?
Regards, Chuck nc8q
next prev parent reply other threads:[~2004-07-15 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 17:31 ANN: mt63lx version 0.5 Tomi Manninen
2004-07-13 3:05 ` chuck gelm
2004-07-13 6:01 ` Matti Aarnio
2004-07-15 3:23 ` chuck gelm
2004-07-15 7:47 ` Matti Aarnio
2004-07-15 13:42 ` chuck gelm [this message]
2004-07-13 20:25 ` [MT63] " Karl Larsen
2004-07-14 19:47 ` Kernel 2.6 Oddness Dave Stubbs
2004-07-14 20:26 ` Tomi Manninen
2004-07-14 21:08 ` Dave Stubbs
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=40F689AC.8020606@gelm.net \
--to=chuck@gelm.net \
--cc=dplatt@radagast.org \
--cc=linux-hams@vger.kernel.org \
--cc=matti.aarnio@zmailer.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;
as well as URLs for NNTP newsgroup(s).