From: Dan Malek <dan@netx4.com>
To: "Brown, David (dbrown03)" <DBrown03@harris.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Serial Port Baud Rate
Date: Tue, 08 Aug 2000 15:47:13 -0400 [thread overview]
Message-ID: <399063C1.994DED9@embeddededge.com> (raw)
In-Reply-To: BE1C564723B3D21191FD0000F840E39801D815ED@rfcmx2.rfc.comm.harris.com
"Brown, David (dbrown03)" wrote:
> .... The modified version runs very well at 115200 Baud,
> with no framing errors.
Thanks. What about other baud rates?
> ..... I also included a few lines which should in theory
> allow very low baud rates, although I have had no reason to test this.
But.....I thought you provided this to me before :-)? I already added
that to source updates.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-08 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-07 20:37 Serial Port Baud Rate Brown, David (dbrown03)
2000-08-08 19:47 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-08 21:37 Brown, David (dbrown03)
2000-08-08 21:59 ` Dan Malek
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=399063C1.994DED9@embeddededge.com \
--to=dan@netx4.com \
--cc=DBrown03@harris.com \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).