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 arch
| BoxMatrix >> System >> dsl_get_arch | @ 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_arch - type | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> AVM-Events - Origin: AVM | ||||||
| Event-Sources: | avm2brcm_xdsld, avm2fiber_xdsld, avm2rtk_xdsld, cable_daemon, dsl_control | ||||||
| Properties: | Firmware: 6.30 - 7.90 | ||||||
| Function: | Broadband frontend architecture 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_arch event informs the system about architecture specific details of the Broadband modem frontend. For
architecture independent details the dsl_get event is 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 the 5490 and 5491.
On 55xx models it was replaced by the fiber_get_arch event.
On Broadcom models this event is sent by avm2brcm_xdsld, on 5490 and 5491 by fiber_monitor.
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 event dsl_get_arch cnt 52805 ... DSL state event / async shm unlock dsl_get_arch cnt 52805
From fiber_monitor --supportdata all fw 7.29:
FIBER event dsl_get_arch cnt 0 ... FIBER state event / async shm unlock dsl_get_arch cnt 0
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 | avm2brcm_xdsld (evsrc) | 3* | 6.85 - 7.39 | Event-Source of avm2brcm_xdsld | AVM |
| Source | evsrc | avm2fiber_xdsld (evsrc) | 2* | 6.83 - 7.12 | Event-Source of avm2fiber_xdsld | AVM |
| Source | evsrc | avm2rtk_xdsld (evsrc) | 1* | 7.29 - 7.30 | Event-Source of avm2rtk_xdsld | AVM |
| Source | evsrc | cable_daemon (evsrc) | 2* | 7.50 - 7.61 | Event-Source of cable_daemon | AVM |
| Source | evsrc | dsl_control (evsrc) | 23* | 6.30 - 7.90 | Event-Source of dsl_control | AVM |
| Sink | evsink | cable_manager (evsink) | 2* | 7.50 - 7.61 | Event-Sink of cable_monitor | AVM |
| Sink | evsink | cable_manager_stat | 2* | 7.50 - 7.61 | Event-Sink of cable_monitor | AVM |
| Sink | evsink | dsl_manager (evsink) | 30* | 6.30 - 7.90 | Event-Sink of dsl_monitor | AVM |
| Sink | evsink | dsl_manager_stat (evsink) | 29* | 6.30 - 7.90 | Event-Sink of dsl_monitor | AVM |
| Sink | evsink | fiber_manager_stat | 2* | 6.83 - 7.01 | Event-Sink of fiber_monitor | AVM |
| 10 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.
