From: Thomas Witzel <witzel.thomas@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Re: RTDM driver questions
Date: Sun, 21 May 2006 21:19:53 +0000 [thread overview]
Message-ID: <200605212119.53330.witzel.thomas@domain.hid> (raw)
In-Reply-To: <if82j3-9ug.ln1@domain.hid>
I have that now, but I'm not really sure how to synchronize the user space
application with the driver, since the driver has of course only a limited
buffer. Practically now I have a 512 sample buffer in the driver that I use
as a double buffer and I copy blocks of 256 to the user on read.
Isn't there a way to have a FIFO between driver and user application and is
there an example somewhere, where I can see how this is done properly ?
Independently of that, if the user space application dies, how can I remove
the driver then ?
Thank you,
Thomas
On Sunday 07 May 2006 22:21, Bernhard Walle wrote:
> Hi Thomas,
>
> Thomas Witzel <witzel.thomas@domain.hid> [2006-05-07]:
> > > Generally spoken, mmap can make sense if you have a significant amount
> > > of data to transfer, not "just" a few kbyte/s. RTDM has the elementary
> > > support for such device interfaces now, and this has already been used
> > > for a frame-grabbing driver.
> >
> > What would be the proper procedure for just a few kbytes ? I expect less
> > than 500 kB./second in my application.
>
> Simply read() / write() ?
>
>
> Regards,
> Bernhard
next prev parent reply other threads:[~2006-05-21 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 15:14 [Xenomai-help] RTDM driver questions witzel.thomas
2006-05-07 21:38 ` Jan Kiszka
2006-05-07 22:02 ` Thomas Witzel
2006-05-07 22:21 ` [Xenomai-help] " Bernhard Walle
2006-05-21 21:19 ` Thomas Witzel [this message]
2006-05-23 9:13 ` Jan Kiszka
2006-05-23 20:29 ` Thomas Witzel
2006-05-23 20:51 ` Jan Kiszka
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=200605212119.53330.witzel.thomas@domain.hid \
--to=witzel.thomas@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.