Marc Roessler
|
Re: RE: Using pulses within the resource Manager Framework
|
Marc Roessler
12/15/2008 6:57 AM
post18587
|
Re: RE: Using pulses within the resource Manager Framework
Well, by "sending pulses across a device" i mean exactly that ;)
I'll elabroate a bit..
Application A is the master
Application B is the slave
The design is inherently asynchronous - this is not our typical "write one block of data and return" like in the driver
cookbooks, but rather "switch to mode X and continue processing in this mode infinitely (even if A dies).. and wake me
in case any errors occur along the way"
B creates /dev/B-ctrl
A opens /dev/B-ctrl and sends commands to B (MsgSend/MsgReceive)
In order for B to signal to A asynchronously (e.g. for errors/status changes), I planned for B to send a pulse to A...
but not via a different channel, but also via this already opened channel (/dev/B-ctrl).
But the problem is i really don't see any easy and clean way to do this in the resource manager framework... of course
you can hook your read and write and devctl handlers here and there... but pulses, asynchronously?
Is synchronous messageing the right choice here anyway? You know that old joke with the multi-purpose-tool "hammer" and
all the nails..
Greetings,
Marc
|
|
|