PSSCH TX Procedures

This include the polar encoding, DMRS specifically for 5G sidelink, the LDPC encoding, virtual and physical resource mapping, NR modulation, etc

What's the point in creating a MR with target a branch that is not develop?

Well, it was simpler to see the changes against the sl-eurecom2 branch and provide the PSSCH TX procedures. If I make an MR to develop, it has the MAC level changes Raymond made, fapi changes from FR (which arent merged). Do you have any recommendations on how to utilize the code in the pending MRs and development while making an MR?

If the goal is just to show the differences to the target branch and not to actually merge to the target branch, then it's OK, I guess. If the goal is actually to merge, we only merge into develop through MRs. If a branch depends on other ongoing MRs, either I would wait to create the MR when the other ones are merged or I would create the MR targeting develop and stating in the description the MRs that need to go first.

added 1 commit

• 3d1b4b88 - Properly building psschsim

Compare with previous version