Contents

#Event (event.js)

### Functions
`if_event(ep, event_name, event)` - Receive an event at some object located at `ep`.  This is a platform defined opaque pointer.

### Interrupts
`int_event(ep, event_name, event)` - Send an event back to *Flok* through an event. The `ep` in this case is dependent on the sub-system. Dispatching is provided through the `evt` (event vector table). On the flok kernel, using, `reg_ivt` and `dereg_ivt` will determine what happens post int_event.  If `ep` is no longer valid, the event in ignored.
For example, the `vc` (view controller) subsystem will receive any events sent when the `ep` is an opaque pointer to a
./app/driver/$PLATFORM/config.yml`)
file is used to compile only the modules into the flok kernel that the driver supports.rface controller from `ui`.

### Kernel spec related
  * `spec_event_handler(ep, event_name, event)` - This function should send the message `spec_event_handler_res(ep, event_name, event)` if called
  * `int_spec_event_dereg` - This function should de-register 3848392 from being an event 

Additionally, you should register the event pointer `3848392` to call the spec_event_handler_res.

Version data entries

21 entries across 21 versions & 1 rubygems

Version	Path
flok-0.0.36	docs/mod/event.md
flok-0.0.35	docs/mod/event.md
flok-0.0.34	docs/mod/event.md
flok-0.0.33	docs/mod/event.md
flok-0.0.32	docs/mod/event.md
flok-0.0.31	docs/mod/event.md
flok-0.0.30	docs/mod/event.md
flok-0.0.29	docs/mod/event.md
flok-0.0.28	docs/mod/event.md
flok-0.0.27	docs/mod/event.md
flok-0.0.26	docs/mod/event.md
flok-0.0.25	docs/mod/event.md
flok-0.0.24	docs/mod/event.md
flok-0.0.23	docs/mod/event.md
flok-0.0.21	docs/mod/event.md
flok-0.0.20	docs/mod/event.md
flok-0.0.19	docs/mod/event.md
flok-0.0.18	docs/mod/event.md
flok-0.0.17	docs/mod/event.md
flok-0.0.16	docs/mod/event.md