BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [Ken Ramey <kramey@as.arizona.edu>] (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Wed Jun 20 08:23:02 2001
Received: from myrthin.as.arizona.edu (IDENT:root@myrthin.as.arizona.edu [128.196.208.164])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f5KEN2e01546
	for <rtl@rtlinux.org>; Wed, 20 Jun 2001 08:23:02 -0600
Received: from as.arizona.edu (IDENT:kramey@localhost [127.0.0.1])
	by myrthin.as.arizona.edu (8.11.0/8.11.0) with ESMTP id f5KEIiX17628
	for <rtl@rtlinux.org>; Wed, 20 Jun 2001 07:18:44 -0700
Sender: kramey@myrthin.as.arizona.edu
Message-ID: <3B30B0C4.9A757AE4@as.arizona.edu>
Date: Wed, 20 Jun 2001 07:18:44 -0700
From: Ken Ramey <kramey@as.arizona.edu>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.17-14 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: rtl@rtlinux.org
Subject: [Fwd: [rtl] RT FIFOs and FIFO handlers]
Content-Type: multipart/mixed;
 boundary="------------BCB6F8ACCDC1842ACB1F19C5"

This is a multi-part message in MIME format.
--------------BCB6F8ACCDC1842ACB1F19C5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



--------------BCB6F8ACCDC1842ACB1F19C5
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

X-Mozilla-Status2: 00000000
Message-ID: <3B2FC2CE.D81524CC@as.arizona.edu>
Date: Tue, 19 Jun 2001 14:23:26 -0700
From: Ken Ramey <kramey@as.arizona.edu>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.17-14 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Barabanov <baraban@fsmlabs.com>
Subject: Re: [rtl] RT FIFOs and FIFO handlers
References: <20010619223910.A8378@fsmlabs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Michael Barabanov wrote:

> You need to use rtf_create_rt_handler, not rtf_create_handler.
>

According to the man page for rtf_create_rt_handler(), it is used to set up a handler which is triggered whenever rtf_put() or rtf_get() is executed by an rt process.  That is
not what I am trying to do.  I need a handler to be triggered when read() or write() are called by a non-rt process.  The documentation says that this is what
rtf_create_handler() is for.

Reading the document more closely, however, reveals an explanation that says this facility is used in conjunction with rtf_get() to read data from the FIFO, after it is put there
with a write().  My problem is the opposite.  I want to put data into the FIFO, _from the rt side_ only when the Linux process is ready to read it.  In other words... when it
executes a read().

It appears that what I am trying to do is not supported by RTLinux.  If anyone can either confirm that or show me the error of my ways and explain how it _can_ be done, I'd
appreciate it.

Thanks.

Ken


--------------BCB6F8ACCDC1842ACB1F19C5--

----- End of forwarded message from owner-rtl@fsmlabs.com -----