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.
Property:dsl get
| BoxMatrix >> System >> dsl_get | @ 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 |
AVM-Event
| AVM-Event: | dsl_get - type | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> AVM-Events - Origin: AVM | ||||||
| Event-Sources: | bbpd, dsl_manager | ||||||
| Properties: | Firmware: 6.30 - 7.90 | ||||||
| Function: | Broadband frontend details | ||||||
Goto: Subevents - Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
This is research in progress and may be partially or completely wrong.
The dsl_get event informs the system about architecture independent details of the Broadband modem frontend. For
architecture specific details the dsl_get_arch or fiber_get_arch events are used. The structure of this event is private, like all
Broadband related events. It is not a DSL specific event, since it is also used to
announce Fiber frontend details.
On 55xx Fiber models and on fw 7.39+ this event is sent by bbpd.
On the remaining DSL models it comes from dsl_monitor.
// From include/uapi/avm/event/gen-types.h // no struct info
Subevents
From dsl_monitor --supportdata all fw 7.29:
DSL TX event dsl_get cnt 6 subevent dsl_params_get cnt 6
From fiber_monitor --supportdata all fw 7.29:
FIBER TX event dsl_get cnt 1 subevent dsl_params_get cnt 1
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 | bbpd (evsrc) | 9* | 7.19 - 7.90 | Event-Source of bbpd | AVM |
| Source | evsrc | dsl_manager (evsrc) | 30* | 6.30 - 7.31 | Event-Source of dsl_monitor | AVM |
| Sink | evsink | ctlmgr_dslparam | 32* | 6.30 - 7.90 | Event-Sink of libbroadband_ui.so for ctlmgr | AVM |
| 3 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.
