Andreas Kurth

- [ ] Get counters into `common_cells`.

Width of user-defined signaling: Extend from single parameter

1

Currently, our interface has one parameter that defines the width of the user signal on all channels. For `struct`s, the `` `AXI_TYPEDEF_*`` macros take a `user_t` that can be different...

Harmonize ports and parameters

13

Let us collect the changes required to harmonize ports and parameters and to minimize incompatibilities with EDA tools. Those changes will be breaking (as in "backwards-incompatible"), so let us make...

We have [`axi_cut`](https://github.com/pulp-platform/axi/blob/master/src/axi_cut.sv) and [`axi_multicut`](https://github.com/pulp-platform/axi/blob/master/src/axi_multicut.sv) for pipelining ([to be unified](https://github.com/pulp-platform/axi/issues/154)), but we currently don't have a module for buffering AXI beats in FIFOs. This gap can be filled by a...

WIP: AXI crosspoint (axi_xp)

7

Adds an AXI crosspoint with homomorphous slave and master ports. This depends on #103 (and currently uses that branch as base, which needs to be changed to `master` once #103...

axi_xbar: Change default master port setting from input to parameter

3

Currently, the _default master port_ feature of `axi_xbar` is set by the input signals `en_default_mst_port_i` and `default_mst_port_i` instead of by `parameter`s. The advantage of using input signals is that the...

Assignments between two `struct` variables, in the style of ```sv assign req_a = req_b; // or always_comb begin req_a = req_b; end ``` are problematic when the `struct` types of...

Replace `axi_cut` and `axi_multicut` by a single module that takes the number of pipeline registers on each channel as parameters (and `0` is a legal value for those parameters).

WIP: AXI4+ATOP Translation Lookaside Buffer (TLB)

1

Here is a first draft of an AXI TLB. I would highly appreciate initial architectural feedback. The concept is similar to that of the RAB (no need to reinvent the...

Post-increment floating-point loads and stores

1

Is it correct that the post-increment extension currently only supports [integer loads and stores](https://github.com/openhwgroup/cv32e40p/blob/8e22c994198ad08f4cacf239d56d98e1cc25627b/rtl/cv32e40p_decoder.sv#L397-L499) but not [floating-point loads and stores](https://github.com/openhwgroup/cv32e40p/blob/8e22c994198ad08f4cacf239d56d98e1cc25627b/rtl/cv32e40p_decoder.sv#L1918-L1999)? If so, are there any plans for enabling that extension...