Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: James Cutler <jwc@stanford.edu>
To: Bob Nielsen <nielsen@oz.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: Serial port recommendations?
Date: Mon, 26 Aug 2002 15:54:15 -0700	[thread overview]
Message-ID: <3D6AB197.1070106@stanford.edu> (raw)
In-Reply-To: 20020826224739.GB16112@bob.n7xy.net

I've had good luck with both PCI and ISA cards from Dolphin.
http://www.dolphinfast.com/

I bought two of the cards, took the UART chips out of one, and
placed them in the other for a 4 port card.


Bob Nielsen wrote:

>I just built a new computer (1 GHz Celeron) for the shack.  It has 2
>onboard serial ports and I was wondering what would be the best way to
>add additional ports.  I figure I need 2-3 for packet, one for rig
>control, one for RTTY/PSK31 PTT and one for CW keying (5-6 total if I
>don't switch connectors).  The motherboard has several PCI slots and
>one ISA, as well as two USB connectors.  I have one old 2-port ISA
>board and I've seen USB-to-serial adapters, but figure a 4-port serial
>adapter might be best.  I haven't seen any of these recently, however. 
>The software I will be using is kernel AX.25 + DX Spider + Xastir
>(packet) and TLF (contesting and general HF use), plus something for
>RTTY and PSK31, (I haven't decided exactly what yet.)
>
>Any suggestions on the best way to get additional serial ports?
>
>73, Bob N7XY
>-
>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
>  
>



  reply	other threads:[~2002-08-26 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 22:47 Serial port recommendations? Bob Nielsen
2002-08-26 22:54 ` James Cutler [this message]
2002-08-26 23:00   ` Curt Mills, WE7U
2002-08-27  7:00   ` Bob Nielsen

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=3D6AB197.1070106@stanford.edu \
    --to=jwc@stanford.edu \
    --cc=linux-hams@vger.kernel.org \
    --cc=nielsen@oz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox