From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Carlos Eduardo de Brito Novaes <carlosnov@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Advice on clock sources for xenomai rtdm driver
Date: Mon, 11 Jul 2011 13:31:39 +0200 [thread overview]
Message-ID: <4E1ADF1B.50904@domain.hid> (raw)
In-Reply-To: <201107101841.28583.carlosnov@domain.hid>
On 07/10/2011 11:41 PM, Carlos Eduardo de Brito Novaes wrote:
> Hello all.
>
> I woud like to ask you some opinion about timers.
> I am slowly working on a real time driver for a acquisition board. It can be
> configured for read up to 32 anaalog channels and has a internal timer that wil
> start the conversion on a programmed time (its a 8254 timer) or the PC ca send
> a command to start conversions to. Sadly, there is no interrupt generated by
> this board, so if using the internal timer the driver has to keep polling some
> io ports to check for data and if any, retrieve it.
> If I can setup a (precise) timer to trigger an interrupt, so I can start the
> conversions and on a know time read back the data. But the interrupt rate
> would be about 1K or a bit more, so RTC would not be a good idea, I think. I
> also read about HPET but it seens to have issues with xenomai and also I read
> that for some reason, some interupts would be lost. Do you guys recommend me
> something? Should I stick with polling and set up some delays with
> usleep_range or there is a good timer on PC boards and weel supported with
> xenomai?
If you are writing an rtdm driver, why not using rtdm timers?
http://www.xenomai.org/documentation/xenomai-2.5/html/api/group__rtdmtimer.html
--
Gilles.
prev parent reply other threads:[~2011-07-11 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 21:41 [Xenomai-help] Advice on clock sources for xenomai rtdm driver Carlos Eduardo de Brito Novaes
2011-07-11 11:31 ` Gilles Chanteperdrix [this message]
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=4E1ADF1B.50904@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=carlosnov@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.