From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rdbfs
Date: Thu, 25 Aug 2005 00:06:45 +0100 [thread overview]
Message-ID: <29ea39c91fd9f15afcf64aecab51e5c0@quintile.net> (raw)
In-Reply-To: <f929342af3f42967538a85e4749b86ab@plan9.bell-labs.com>
I beleive the uarts still default to FIFOs disabled.
I use rs422 on plan9 (on a 1.6Ghz machine) at 115Kbaud reliably -
as long as the fifo is enabled (the manpage is a bit out of date,
though the source isn't). Having said this I _do_ have trouble at 115K
on my 400Mhz laptop, which is sad as it could be really useful.
Updating the manpage moves one click up the To-do list...
-Steve
next prev parent reply other threads:[~2005-08-24 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 20:33 Brantley Coile
2005-08-24 20:53 ` Russ Cox
2005-08-24 22:50 ` Sape Mullender
2005-08-24 22:56 ` Brantley Coile
2005-08-24 23:19 ` Russ Cox
2005-08-24 23:23 ` Brantley Coile
2005-08-25 4:33 ` Tim Newsham
2005-08-24 23:06 ` Steve Simon [this message]
2005-08-25 2:41 ` Scott Schwartz
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 17:00 Brantley Coile
2005-08-24 17:13 ` Russ Cox
2005-08-24 17:25 ` Brantley Coile
2005-08-24 17:39 ` Russ Cox
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=29ea39c91fd9f15afcf64aecab51e5c0@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/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).