From: Niall Parker <niall@ve7hex.ampr.org>
To: Phil <phillor@telstra.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: USB converters and old hardware
Date: Thu, 15 Apr 2010 08:55:47 -0700 [thread overview]
Message-ID: <4BC73703.9030400@ve7hex.ampr.org> (raw)
In-Reply-To: <201004151151.38923.phillor@telstra.com>
Phil wrote:
> On Wed, 14 Apr 2010 03:37:03 pm Douglas Cole wrote:
>> I have to agree, I use the Keyspan adapters at work and at home.
>> They work for me as well, both the multiport devices as well as the
>> single port ones (USA19-HS)...
>> Port replicator for my work HP laptop gives me a 'real' serial port
>> (COM1 in Win32 land)...
>>
>
> Thanks Doug and Stuart for the extra information.
>
> I have an unbranded duel port USB to serial converter that works perfectly
> with all sorts of serial devices except my Baycom clone modem. Can
> anyone confirm that the Keyspan converter will allow me to use my modem
> once again? The tripplite site does not say that their converter provides a
> genuine serial port and I suspect that it doesn't.
>
> Even though Soundmodem works well I have found that my Baycom
> modem is far superior in that it will decode packets just above the noise
> level. Rather than fool around with USB to serial converters maybe I might
> be better off looking for a used TNC?
A Baycom style modem relies on a 'real' serial port because it _isn't_
using the serial port for typical asynchronous communications but rather
twiddling the control/data lines at a bit level via the registers of
the once ubiquitous 8250 (and clones) UART. While it is conceivable that
one could write a device driver for the USB chips that does the same
thing (in particular the FTDI USB/serial chips have some options for bit
level control), running the Baycom driver on top of an asynch emulation
USB driver is going to be problematic with all the extra latencies
involved. A fast enough PC might do it, but as you've found it often
won't work at all.
A serial TNC on the other hand just talks plain ole asynch serial and
will work fine.
... Niall
next prev parent reply other threads:[~2010-04-15 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 5:08 USB converters and old hardware Phil
2010-04-08 10:20 ` Mike McCarthy, W1NR
2010-04-09 1:09 ` Phil
2010-04-13 14:42 ` walter harms
2010-04-13 17:52 ` IT2 Stuart Blake Tener, USNR
2010-04-14 5:37 ` Douglas Cole
2010-04-14 15:18 ` IT2 Stuart Blake Tener, USNR
2010-04-15 1:51 ` Phil
2010-04-15 14:49 ` IT2 Stuart Blake Tener, USNR
2010-04-15 17:47 ` USB converters and old hardware (in general) Dave Platt
2010-04-15 17:48 ` USB converters and old hardware (Baycom in particular) Dave Platt
2010-04-15 19:22 ` Tomi Manninen
2010-04-15 20:05 ` Adam Sampson
2010-04-15 20:41 ` Dave Platt
2010-04-15 15:55 ` Niall Parker [this message]
2010-04-15 16:56 ` USB converters and old hardware IT2 Stuart Blake Tener, USNR
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=4BC73703.9030400@ve7hex.ampr.org \
--to=niall@ve7hex.ampr.org \
--cc=linux-hams@vger.kernel.org \
--cc=phillor@telstra.com \
/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.