From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Carlos Eduardo de Brito Novaes <carlosnov@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Writing a new driver, shoud use message pipes or shared memory?
Date: Fri, 01 Jul 2011 09:57:27 +0200 [thread overview]
Message-ID: <4E0D7DE7.50803@domain.hid> (raw)
In-Reply-To: <201106301212.47433.carlosnov@domain.hid>
On 06/30/2011 05:12 PM, Carlos Eduardo de Brito Novaes wrote:
> Hello all!
> Hope this question fits to the scope of the list.
>
> I got a PCI acquisition board and wish to write a xenomai driver for it. I had
> did this before with an old ISA board and used memory heaps to exchange data
> from kernel (configuration and mainly acquisition routines) and the real time
> processing task.
>
> Now, I would like to know if I can use only message pipes for this kind of
> application. I would like to use it so the entire proccess became more "unix
> like", using memory heaps I think that the internals of the driver are exposed
> and the any misfuncion can arise due to bad data passed from programmers. Is
> this right?
>
> Can message pipes provide hard real time timings, about 1K/10K samples per
> second and about 100 bytes on each sample?
Hi,
you probably should use the RTDM skin to write a driver. So, use the
"read" call to get data, or if there is a big volume, use some mmaped
aread, using rtdm_mmap_to_user.
Regards.
--
Gilles.
next prev parent reply other threads:[~2011-07-01 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 15:12 [Xenomai-help] Writing a new driver, shoud use message pipes or shared memory? Carlos Eduardo de Brito Novaes
2011-07-01 7:57 ` Gilles Chanteperdrix [this message]
2011-07-01 17:23 ` [Xenomai-help] Writing a new driver, Skin differences Carlos Eduardo de Brito Novaes
2011-07-02 20:13 ` Gilles Chanteperdrix
2011-07-02 20:38 ` Luis Rossi
2011-07-02 20:47 ` Gilles Chanteperdrix
2011-07-03 1:47 ` Carlos Eduardo de Brito Novaes
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=4E0D7DE7.50803@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.