Skip to content

Reformat address table to have a single line per endpoint

Following up from the discussion in !40 (merged):

> This is more a comment on the style, not only for this entry but for everything.
> Sometimes I find quite tedious to deal with this format of the address table. I would use something like this (I am not adding the `orbits_per_packet` entry)
> ```
> ...
>             "filler_orbits_seen_orbits"      : { "width": 32, "address": "0x4c",  "offset":  0, "metric": "counter", "writable": false, "exposable": true  },
>             "filler_orbits_dropped_orbits"   : { "width": 32, "address": "0x50",  "offset":  0, "metric": "counter", "writable": false, "exposable": true  },
>             "axi_backpressure_seen_info"     : { "width":  1, "address": "0x54",  "offset":  0, "metric": "gauge"  , "writable": false, "exposable": true  },
>             "orbit_exceeds_size_info"        : { "width":  1, "address": "0x54",  "offset":  1, "metric": "gauge"  , "writable": false, "exposable": true  },
>             "waiting_for_orbit_end_info"     : { "width":  1, "address": "0x54",  "offset":  2, "metric": "gauge"  , "writable": false, "exposable": false },
>             "autorealigns_total"             : { "width": 32, "address": "0x58",  "offset":  0, "metric": "counter", "writable": false, "exposable": true  },
>             "orbit_length_bxs"               : { "width": 32, "address": "0x5c",  "offset":  0, "metric": "gauge"  , "writable": false, "exposable": true  },
>             "algo_version"                   : { "width": 24, "address": "0x60",  "offset":  0, "metric": "gauge"  , "writable": false, "exposable": true  },
> ...
> ```
> which would be similar to the style of the address tables for the DTH.
Edited by Dinyar Rabady
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information