From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-serial@vger.kernel.org
Subject: Re: interrupt programming
Date: Thu, 22 Jul 2004 14:20:34 +0200 [thread overview]
Message-ID: <20040722122034.GH18676@lug-owl.de> (raw)
In-Reply-To: <BAY15-F22wSs3yoW3Al0005522c@hotmail.com>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Thu, 2004-07-22 12:02:37 +0200, Sayang Oin <sayangoin@hotmail.com>
wrote in message <BAY15-F22wSs3yoW3Al0005522c@hotmail.com>:
> I've written a programm to communicate with a external UART device through
> /dev/ttyS0.
> I use POSIX and Timer but unfortunately is not working well.
What do you need timers for? If you're waiting for data, just use
select(). That even allows you to perform other actions every now and
then.
> Is it possible to use Interrupt to read and write datas through the serial
> port?
Linux' serial driver should work interrupt-driven most of the time. Only
in rare cases it'll poll the serial chip, but I think that's not really
your problem.
Please tell us what you *really* need to do. Then, we'd help you.
Sources of your application to comment on weren't wrong, too...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-22 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 10:02 interrupt programming Sayang Oin
2004-07-22 12:20 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 7:24 Sayang Oin
2004-07-26 8:08 ` Jan-Benedict Glaw
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=20040722122034.GH18676@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-serial@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