From: Ivan Korzakow <ivan.korzakow@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: fast communication problem
Date: Wed, 16 Nov 2005 16:43:22 +0100 [thread overview]
Message-ID: <a59861030511160743l19b7be6bn@mail.gmail.com> (raw)
Hi List,
I'm running a 2.6.14 linux on 96 MHz MIPS processor. I need to cope
with a device that sends a byte of data every 50 microsecond through
an UART with no FIFO. What would be the best (well, the least
horrible) way to handle that ? The good point is that I know when the
communication starts.
Any idea, any help, any "good luck" will be much appreciated !
Thanks in advance,
Ivan
next reply other threads:[~2005-11-16 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:43 Ivan Korzakow [this message]
2005-11-16 16:10 ` linux-os (Dick Johnson)
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=a59861030511160743l19b7be6bn@mail.gmail.com \
--to=ivan.korzakow@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®