Thread (5 messages) 5 messages, 3 authors, 2012-05-12

interface for a hardware trigger driver

From: Philipp Ittershagen <hidden>
Date: 2012-05-10 14:16:36

Hi Andre,

On Thu, May 10, 2012 at 03:18:49PM +0200, Andre Haupt wrote:
Or better, reading the device file blocks and returns the trigger status (none,
triggered, aborted) and writing to the device file wakes up the sleeping
processes.

So cat /dev/mydevice would block until an interrupt occurs or someone does
an echo foo > /dev/mydevice.
this is even better, yes.
I vagely remember having done that in the first place. I cant remember
why i went with the ioctl stuff back then, though.
It's always good to drop ioctl code ;) Using the semantics you mentionend
above for read() and write(), the code gets simpler and easier to follow IMHO.


Greetings,

  Philipp
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help