Hi,
> I'm having the exact same problem. I installed a handler that
> should start upon an read atempt from the user space but never starts! To
> solve this I used a workaround that consists in a write to a rt fifo that
> starts a handler that writes the info to another rt fifo so the user
> process can read it on demand. This is not a simple read perform from the
> user space. In my task it is imperative than when a read atempt from the
> user space is made the rt task responds imediately writing to that fifo.
> If it is a bug I would be quite glad if someone fixed it.
Imo it's a bug/design fault- if I need to write to the rtf to kick the thread
to fill me the buffer I don't need a handler on user read ops.
To Nathan: Imo to poll() is an access. I ask for new data - if there are new I
get it from the buffer. If I don't want to get the prepered data I can leave
the handler - the task is reponsible for filling the rtf with data even is
there is no callback. Therefore poll() gets only data if the kernel task has
data. handler callback is asyncronous to the rt task.
Regards
Olaf
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
