From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] rdbfs
Date: Wed, 24 Aug 2005 16:53:41 -0400 [thread overview]
Message-ID: <ee9e417a05082413536f5351dc@mail.gmail.com> (raw)
In-Reply-To: <7af9ba0f18a193d111fd984bfb562579@coraid.com>
> could it be that some other process is stealing bytes
> out of the uart? how do i make sure that's not happening?
that's really unlikely given that the kernel is splhi
looping to poll the uart.
russ
next prev parent reply other threads:[~2005-08-24 20:53 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 [this message]
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
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=ee9e417a05082413536f5351dc@mail.gmail.com \
--to=russcox@gmail.com \
--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).