If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.

AVM-Events

From BoxMatrix
(Redirected from Events)


BoxMatrix >> System >> AVM-Events @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Devices Filesystems Partitions Sockets Netlink Pipes Interfaces Bridges Ports Events Sources Sinks AVMIPC Processes Watchdogs Memory Slab Vmalloc ProcFS SysFS Research

Info
FRITZ!OS contains an event management system, used to trigger functions in processes. Listening receivers register Event-Sinks, senders which fire up AVM-Events register Event-Sources. A sink registers the events it wants to be notified about, and gets filtered notifications from the event manager. Multiple sinks can register for the same event, and all get notified about it once the registered event occurs. This is managed by libavm_event.so.

AVM-Events[edit]

See also the table with FRITZ!OS 7.50+ news below and the total Overview of F!OS news!

Daily updated index of all events found scanning Supportdata-Probes. Last update: 2024-04-06 08:31 GMT.
The label (event) in the AVM-Event column shows there are other objects in this wiki using this name.
The Mod column shows the amount of models using the respective event. Click the column header to sort by this number.
Note that the Event-Statistic in supportdata.basis is pretty new, so only firmware 6.20+ is covered.

Goto:   A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z   -   Index

FRITZ!OS 7.5x[edit]

AVM-Events which are new in FRITZ!OS 7.50+ and its 7.39+ Labors. See also the total Overview of F!OS news!
Click the Firmware column header twice to list the latest additions first.

Research[edit]

Sometimes supportdata contains event names like undef-31. This happens in labors if the kernel is older than userspace.
The BoxMatrix scanner renames them back that is why it is useful to have the absolut event id numbers:

// From include/uapi/avm/event/gen-types.h

struct _avm_event_header {
	enum _avm_event_id id;
};

enum _avm_event_id {
  wlan_client_status = 0,
  wlan_event = 1,
  wlan_power = 2,
  autoprov = 7,
  usb_status = 8,
  dsl_get_arch_kernel = 11,
  dsl_set_arch = 12,
  dsl_get_arch = 13,
  dsl_set = 14,
  dsl_get = 15,
  dsl_status = 16,
  dsl_connect_status = 17,
  push_button = 19,
  telefon_wlan_command = 20,
  capiotcp_startstop = 21,
  telefon_up = 22,
  reboot_req = 23,
  appl_status = 24,
  led_status = 25,
  led_info = 26,
  telefonprofile = 27,
  temperature = 28,
  cpu_idle = 29,
  powermanagment_status = 30,
  powerline_status = 31,
  ethernet_connect_status = 33,
  powermanagment_remote = 34,
  log = 35,
  remotewatchdog = 36,
  rpc = 37,
  remotepcmlink = 38,
  piglet = 39,
  pm_ressourceinfo_status = 40,
  telephony_missed_call = 41,
  telephony_tam_call = 42,
  telephony_fax_received = 43,
  internet_new_ip = 44,
  firmware_update_available = 45,
  smarthome_switch_status = 46,
  telephony_incoming_call = 47,
  mass_storage_mount = 48,
  mass_storage_unmount = 49,
  checkpoint = 50,
  cpu_run = 51,
  ambient_brightness = 52,
  fax_status_change = 53,
  fax_file = 54,
  telephony_call_finished = 55,
  smarthome = 56,
  fiber_set_arch = 57,
  fiber_get_arch = 58,
  user_source_notify = 63,
  last,
};

TODO:

Fact-Box