All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: trem <tremyfr@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] RTDM context_size question
Date: Thu, 23 Aug 2007 22:33:56 +0200	[thread overview]
Message-ID: <46CDEF34.2030003@domain.hid> (raw)
In-Reply-To: <46C9FFDA.8030200@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

Hi Philippe,

sorry for the delay - I was and still am short on time.

trem wrote:
> Hi
> 
> Oh, I understand your point of view, and I found it fine. We do an
> example quite complete (and with some sense), and we split it into step.
> 
> The first complete example could contain :
> - global buffer (one for all device)
> - device buffer (one for each device)
> - local buffer (one for each open)
> - synchronization: semaphore used to block read when no data are ready
> - ioctl: used to to select the active buffer (ie global, device, local)
> 
> Now, how to split it ? I propose :
> 
> tut01: global buffer + read/write
> tut02: {global, device, local} buffer + ioctl + read/write
> tut03: {global, device, local} buffer + ioctl + read/write + synchronization
> 

Let's write the full example first, look at the result, and then decide
about the best split-up.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  parent reply	other threads:[~2007-08-23 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 12:04 [Xenomai-help] RTDM context_size question Steven Kauffmann
2007-08-16 17:59 ` Jan Kiszka
2007-08-16 20:59   ` trem
2007-08-17  8:17     ` Jan Kiszka
2007-08-17 22:43       ` trem
     [not found]       ` <46C5E4AC.1090608@domain.hid>
2007-08-18  6:34         ` [Xenomai-core] " Jan Kiszka
2007-08-20 21:15           ` trem
     [not found]           ` <46C9FFDA.8030200@domain.hid>
2007-08-23 20:33             ` Jan Kiszka [this message]
2007-08-23 20:43               ` trem

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=46CDEF34.2030003@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=tremyfr@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.