This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/linux-dect@lists.osmocom.org/.
Patrick McHardy kaber at trash.netOn Thu, 9 Aug 2012, Frédéric LECAILLE wrote: > when I choose a FP I see such kernel logs: > > [24063.168612] TX 647.01.11: FT T-MUX: N-channel > [24063.168620] TX 647.01.11: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 27 PSCN: 25 > [24063.173600] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 > [24063.174037] cell0: RX 647.02.00: timer e30085fc: 647.2.0 > [24063.174092] cell0: RX 647.02.00: timer e30085fc: schedule for 647.3.0 > [24063.178605] cell0: RX 647.01.23: timer e30085dc: 647.1.23 > [24063.178615] cell0: RX 647.01.23: timer e30085dc: schedule for 647.2.23 > [24063.178624] TX 647.02.11: FT T-MUX: N-channel > [24063.178633] TX 647.02.11: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 27 PSCN: 26 > [24063.183599] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 > [24063.184028] cell0: RX 647.03.00: timer e30085fc: 647.3.0 > [24063.184064] cell0: RX 647.03.00: timer e30085fc: schedule for 647.4.0 > [24063.188603] cell0: RX 647.02.23: timer e30085dc: 647.2.23 > [24063.188613] cell0: RX 647.02.23: timer e30085dc: schedule for 647.3.23 > [24063.188622] TX 647.03.11: FT T-MUX: N-channel > [24063.188633] TX 647.03.11: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 27 PSCN: 27 > [24063.193596] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 > [24063.194037] cell0: RX 647.04.00: timer e30085fc: 647.4.0 > [24063.194093] cell0: RX 647.04.00: timer e30085fc: schedule for 647.5.0 > [24063.198606] cell0: RX 647.03.23: timer e30085dc: 647.3.23 > [24063.198613] cell0: RX 647.03.23: timer e30085dc: schedule for 647.4.23 > [24063.198618] TX 647.04.11: FT T-MUX: N-channel > [24063.198625] TX 647.04.11: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 27 PSCN: 23 > [24063.203599] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 > [24063.204036] cell0: RX 647.05.00: timer e30085fc: 647.5.0 > [24063.204092] cell0: RX 647.05.00: timer e30085fc: schedule for 647.6.0 > [24063.208603] cell0: RX 647.04.23: timer e30085dc: 647.4.23 > [24063.208609] cell0: RX 647.04.23: timer e30085dc: schedule for 647.5.23 > [24063.208614] TX 647.05.11: FT T-MUX: N-channel > [24063.208621] TX 647.05.11: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 27 PSCN: 24 > [24063.213604] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 > [24063.214028] cell0: RX 647.06.00: timer e30085fc: 647.6.0 > [24063.214063] cell0: RX 647.06.00: timer e30085fc: schedule for 647.7.0 > > > dect-llme-scan never display any message… Sure, a FP can't scan. I suggest you test it on real hardware, there are going to be no noticable changes on vtrx.