From: Alan Crosswell <n2ygk@weca.org>
To: Jim Kusznir <jkusznir@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: KISS eprom images
Date: Wed, 25 Aug 2010 17:27:05 -0400 [thread overview]
Message-ID: <4C758AA9.6070804@weca.org> (raw)
In-Reply-To: <AANLkTik+LSn1BVzCbkF=iFhC1VxG7KThbrEYrKfr01oN@mail.gmail.com>
Jim,
If you're using Linux (or windows for that matter), you'll probably get
better performance by just using Tom Sailer's soundmodem with a
soundcard (either PCI or external USB -- but a good quality one) rather
than trying to use 1980's-era TNC2's. I have several long-running
production digipeaters running with my aprsdigi code and Tom's
soundmodems -- albeit all at 1200 baud. I've played around a little
with 9600 baud but don't know enough to say anything useful.
See http://www.baycom.org/~tom/ham/soundmodem/ and
http://www.baycom.org/~tom/pcf/ptt_circ/ptt.html for the PTT circuit for
serial or parallel ports.
73 de Alan N2YGK
On 8/25/2010 5:10 PM, Jim Kusznir wrote:
> Hi all:
>
> This is a bit off topic, but my intended use is with linux!
>
> I'm searching high and low for any KISS or (preferably) 6pack rom
> images so that I can load my TNCs up with them and get a good, solid
> linux interface. The vendor-supplied TNC image is not up to snuff for
> this on one of my TNCs, and my other use is retrofitting my stack of
> TheNet nodes with a linux embedded system, and KISS roms.
>
> So, if anyone can provide me TNC2-compatible (and PK96 if available --
> I have one PK96, 3 TNC2s, and 2 PacCOM SPRINT-2s), I'd greatly
> appreciate it.
>
> --Jim, K7LL
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2010-08-25 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 21:10 KISS eprom images Jim Kusznir
2010-08-25 21:27 ` Alan Crosswell [this message]
2010-08-25 21:43 ` Andre Lohan
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=4C758AA9.6070804@weca.org \
--to=n2ygk@weca.org \
--cc=jkusznir@gmail.com \
--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.