Experimental irtoy driver version keeping device open

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Experimental irtoy driver version keeping device open

Bengt Martensson-2
Good morning,

I have created an experimental version of the IrToy driver, not closing
the device between the invocations (i.e. not opening and closing in init
and deinit). It also logs the resolved path name of the device (i.e., if
the device given was a symlink, the target of that link). As opposed to
the original driver, it closes on exiting the program.  (Thanx to Helen
Foster for finding this.)

For debugging, it turns out that adding debugging LEDs, as I described
in
http://dangerousprototypes.com/forum/viewtopic.php?f=29&t=7358p://dangerousprototypes.com/forum/viewtopic.php?f=29&t=7358 
is quite useful.

With some extra effort, the "new" and the old behavior can be made
runtime selectable with a driver parameters (-A or --driver-options to
lircd).

It is available in my Sourceforge fork
https://sourceforge.net/u/bengtmartensson/lirc/ci/experimental-irtoy/ 
Only irtoy,c has been changed.

Greetz,

Bengt (Barf at the Dangerous prototypes forum)

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e