Project

General

Profile

Bug #1665

Multi-TRX does not support configurations without TRX0

Added by laforge over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
osmo-bts-litecell15
Target version:
-
Start date:
03/21/2016
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

In normal cases, we expect to have
  • 1...n phy_links
    • with each 1..n phy_instances
  • each phy_instance mapped to one TRX
However, in some cases people want to have configurations where certain TRX are by-passed. Imagine situations where a TRX has become defective in some way.
In such cases, we might end up having:
  • any number of phy_links/phy_instances without a TRX mapped to them
  • TRX0 mapped to any of the remaining phy_instances.

We should properly support such configurations and verify that they are functional. Verification should happen on osmo-bts-litecell15.

History

#1 Updated by msuraev over 2 years ago

  • Status changed from New to In Progress

Fix sent for review to ML.

#2 Updated by laforge over 2 years ago

  • Priority changed from Normal to High

#3 Updated by msuraev about 2 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from msuraev to laforge

Fix has been merged to osmo-bts master.

#4 Updated by laforge about 2 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)