Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !1468

Merged
Created Nov 06, 2023 by Kirill Smelkov@kirrOwner

software/ors-amarisoft: ru/lopcomm: Simplify and clarify cu_config.jinja2.xml

  • Overview 1
  • Commits 1
  • Changes 2

We can use mathematical relation in between ports, channels and tx/rx endpoints to bring structure and clarity in RU setup.

Also, while on it, document how tx/rx data flow are organized as it was not clear just from reading ORAN specs and I had to deduce it.

/cc @jhuge, @lu.xu, @xavier_thompson, @Daetalus

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: y/multiru-lopcomm-cumath
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7