Request: Return DRAM hash logic to module

[dpetrisko]

The DRAM striping logic used to be contained in this hash_function module:

bsg_manycore/v/bsg_manycore_eva_to_npa.v

Line 81 in 909dbbf

hash_function #(

Now it's directly embedded in the EVA to NPA mapping:

bsg_manycore/v/bsg_manycore_eva_to_npa.v

Line 87 in 0f657f2

wire [vcache_row_id_width_lp-1:0] vcache_row_id = eva_i[2+vcache_word_offset_width_lp+x_subcord_width_lp+:vcache_row_id_width_lp];

The BlackParrot to MC bridge uses this hash function to map its own DRAM to the correct V$ banks. https://github.com/bespoke-silicon-group/hb_bigblade/blob/master/bigblade_bp_unicore/v/bp_cce_to_mc_bridge.sv#L220 However, it doesn't use the rest of the EVA-NAP map.

Can we put this logic back in a dram_hash_function module? BlackParrot will not be the only accelerator which faces this issue

[taylor-bsg]

@tommydcjung do you want to do the refactor or have dan do a pull request?

[tommydcjung]

I can do the refactor.