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.

0
U

Property:rpc (event)

From BoxMatrix


BoxMatrix >> System >> rpc (event) @ 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
  
Name-Collision - multiple objects in this wiki use the name rpc!
rpc (avmcmd) Remote command executer for Puma6 / Puma7 models.
rpc (event) ptestd remote commands
rpc (static) TODO
rpc (tmpdir) TODO
rpc (vartar) TODO

AVM-Event

Goto:   Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser

Details

The rpc event is used for Inter-CPU communication of ptestd instances on Puma6/7 models.

On Puma6 and Puma7 models FRITZ!OS is running on the ATOM CPU, while the cable modem frontend runs on the ARM CPU.
ptestd is a production test helper daemon running on both Linux instances to perform calibration and tests during production.
To communicate with each others each instance has a ptestd_source event source and a ptestd sink to exchange rpc events.

An rpc event can be a command or a reply. For example: An ATOM ptestd sends a command_to_arm rpc event from its
ptestd_source. the ARM ptestd receives it at its ptestd sink. It then responds by a reply_to_atom rpc event from its
ptestd_source which the ATOM ptestd receives at its ptestd sink. This principle works in both directions.

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

#define AVM_EVENT_RPC_MAX_MESSAGE_SIZE 240

struct avm_event_rpc {
	enum _avm_rpctype type;
	unsigned int id;
	unsigned int length;
	unsigned char message[0];
};

enum _avm_rpctype {
	command_to_arm = 0,
	command_to_atom = 1,
	reply_to_arm = 2,
	reply_to_atom = 3,
};

Dependencies

Daily updated index of all dependencies of this event. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.

Relation Typ Object Mod Firmware Info Origin
Source evsrc ptestd_source 14* 6.24 - 7.61 Event-Source of ptestd AVM
Sink evsink ptestd (evsink) 14* 6.24 - 7.61 Event-Sink of ptestd AVM
2 dependencies for this event

Model-Matrix

Daily updated index of the presence, path and size of this event for each model. Last update: GMT.
Showing all models using this event. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.

Missing Supportdata

The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.

SMW-Browser

Information is currently being retrieved from the backend.