From: "Bruno Tréguier" <Bruno.Treguier@shom.fr>
To: Miroslav Skoric <skoric@eunet.rs>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: RS232-USB conversion
Date: Tue, 18 Oct 2011 23:00:11 +0200 [thread overview]
Message-ID: <4E9DE8DB.9060906@shom.fr> (raw)
In-Reply-To: <4E9DDC6B.8080702@eunet.rs>
Le 18/10/2011 à 22:07, Miroslav Skoric a écrit :
> OK guys, thank you all for your advices ...will see about compiling FBB
> when I return from a conference trip. Btw, after a long time of avoiding
> to purchase a laptop/notebook comp (and still living well without a
> cellphone :-)), I have been thinking about an inexpensive portable comp
> that could run not only PPT (or similarly formatted) scientific
> presentations, but also to give me an opportunity to run my TNC2S (an
> old German-made TNC), which connects over RS232. I do not know if some
> of you have experience with some of those adapters that convert an USB
> output of a laptop to a RS232 connector of a TNC. I heard that some
> adapters (if not all) come with a kind of software that makes them
> thinking that the computer still has COM1, COM2, etc, but I don't know
> if such software works only in M$ world or/and in Linux too. (In the
> other words, I would like to have a relatively modern machine, but to
> avoid buying an expensive one that is still equipped with RS232.)
>
> Opinions?
Hi Miroslav,
I guess all those devices come at least with a Windows driver, but
regarding Linux you shouldn't have any problem either, as most of the
converters out there are based on FTDI or Prolific chipsets, which have
been supported out-of-the-box by linux kernels for at least several
years now. They usually are seen as /dev/ttyACMxx or /dev/ttyUSBxx
respectively, and flow-control signals are also correctly dealt with.
However, I heard (or rather read) some people stating that though all
devices seemed to work fine for rig-control purposes, they had problems
when using Prolific-based converters for FSK, which weren't quick enough
(the issue seemed to be driver-related). This information is quite old
now, but if you want to avoid problems, you should probably favour
FTDI-based converters if you intend to use them with your TNC.
Best regards,
Bruno - F8FIV
--
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:[~2011-10-18 21:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 8:18 Compiling FBB f6bvp
2011-10-14 22:10 ` Miroslav Skoric
2011-10-14 22:20 ` Dave Platt
2011-10-15 7:55 ` Bernard, f6bvp
2011-10-15 10:00 ` Marc Coevoet
2011-10-17 11:25 ` Bernard, f6bvp
2011-10-18 20:07 ` RS232-USB conversion (was: Compiling FBB) Miroslav Skoric
2011-10-18 20:21 ` Gordon JC Pearce
2011-10-18 21:16 ` RS232-USB conversion Dave Platt
2011-10-18 21:00 ` Bruno Tréguier [this message]
2011-10-21 4:02 ` Compiling FBB David Ranch
2011-10-21 10:15 ` Bernard, f6bvp
2011-10-21 17:11 ` Lee Woldanski
2011-10-21 12:04 ` Thomas Osterried
2011-11-08 20:05 ` Patrick Ouellette
2011-11-08 20:12 ` Thomas Osterried
2011-11-08 21:22 ` Ralf Baechle DL5RB
2011-11-08 21:39 ` Bill Vodall
2011-11-08 22:09 ` Patrick Ouellette
2011-11-09 1:22 ` David Ranch
2011-11-09 7:09 ` Marc Coevoet
2011-11-09 9:31 ` Thomas Osterried
2011-11-09 9:36 ` Marco Di Martino (IW2OHX)
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=4E9DE8DB.9060906@shom.fr \
--to=bruno.treguier@shom.fr \
--cc=linux-hams@vger.kernel.org \
--cc=skoric@eunet.rs \
/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.