From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Joe Barr'" <joe@pjprimer.com>,
"'Linux Kernel mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: Serial port blues
Date: Sun, 21 Jan 2007 00:09:39 -0500 [thread overview]
Message-ID: <09dd01c73d1a$5a71a5f0$294b82ce@stuartm> (raw)
In-Reply-To: <1169242654.20402.154.camel@warthawg-desktop>
From: On Behalf Of Joe Barr
> I'm forwarding this post by the author of a great little program for
> digital amateur radio on Linux, because I'm curious whether or not the
> problem he is seeing can be resolved outside the kernel.
From: w1hkj [mailto:w1hkj@w1hkj.com]
> I am now convinced that the current serial port drivers
> available to us
> on the Linux platform WILL NOT support CW and/or RTTY that is
> software
> generated in a satisfactory manner.
I don't know what FSK/CW/RTTY/BAUDOT is.
> Direct access to the serial port(s) is a kernel perogative in Linux.
> Only kernel level drivers are allowed such port access.
Not true.
> Until such time as new information becomes available I am going to
> comment out all references to CW and / or FSK via RTS/DTR. I also
> question how useful the FSK on TxD (UART derived) might be to
> most users
> since the 45.45 baudrate is not available in the serial port driver.
> That function will also be commented out.
You may be confusing the old-style baud rate lookup table (B9600 et
al) with the actual capabilities of the serial port. The lookup table
has a limited number of baud rates. You can get more rates than that
using a custom divisor. Most motherboard-based serial ports are
clocked at 1.8432 Mhz. The UART does 16 samples per bit time, yielding
a max baud rate of 115200.
115200 / 25 yields 4608, which is a 1.4% error rate from 4545. This
may or may not be acceptable. 115200 / 2535 yields 45.44, which is a
0.01% error rate, which is likely acceptable.
> Sorry folks, but we win some and lose some.
We make serial port boards with very flexible UARTS. 4545 exactly is
achievable. 45.45 too. Linux supported.
..Stu
--
We make multiport serial products.
http://www.connecttech.com/
(800) 426-8979
next prev parent reply other threads:[~2007-01-21 5:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 21:37 Serial port blues Joe Barr
2007-01-20 17:36 ` Willy Tarreau
2007-01-21 5:54 ` Theodore Tso
2007-01-21 7:05 ` Willy Tarreau
2007-01-21 14:04 ` Johannes Stezenbach
[not found] ` <2f4958ff0701210650w4fa0138di6a5026de8a0823dc@mail.gmail.com>
2007-01-21 14:58 ` Willy Tarreau
[not found] ` <2f4958ff0701210710r743c1821n9af23a050c847a7@mail.gmail.com>
2007-01-21 18:52 ` Theodore Tso
[not found] ` <2f4958ff0701211105p4f7e3e86x8aaf14566112bc51@mail.gmail.com>
2007-01-21 19:30 ` Theodore Tso
2007-01-21 18:55 ` Theodore Tso
2007-01-21 5:09 ` Stuart MacDonald [this message]
2007-01-21 7:07 ` H. Peter Anvin
2007-01-21 7:08 ` H. Peter Anvin
2007-01-21 20:44 ` H. Peter Anvin
2007-01-22 11:37 ` Alan
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='09dd01c73d1a$5a71a5f0$294b82ce@stuartm' \
--to=stuartm@connecttech.com \
--cc=joe@pjprimer.com \
--cc=linux-kernel@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.