On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote:
Updated patch attached <usdect.diff>
Ok thank you a lot Patrick.
Here are the results:
with your last patch:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
*The frequency is always 0 MHz*
The kernel logs seems to be OK:
[15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27
So I have tried your last patch with mine to force the rf_band to 1:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on...
About trx2:
dect-transceiver-list --name trx2 DECT Transceiver trx2: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0
slot 0: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
(no a-crc-errors)
If I remember well, with only my patch which forces the rf_band to 3 we got for trx2:
dect-transceiver-list --name trx2 I see that slot0 is scanning:
DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0
if my analyze is correct, the virtual interface vtrx is scanning, not the physical one… as fat as I understand the command outputs…
On Aug 9, 2012, at 8:02 PM, Frédéric LECAILLE wrote:
On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote:
Updated patch attached <usdect.diff>
Ok thank you a lot Patrick.
Here are the results:
with your last patch:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
*The frequency is always 0 MHz*
The kernel logs seems to be OK:
[15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27
So I have tried your last patch with mine to force the rf_band to 1:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on...
About trx2:
dect-transceiver-list --name trx2 DECT Transceiver trx2: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0
slot 0: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
(no a-crc-errors)
If I remember well, with only my patch which forces the rf_band to 3 we got for trx2:
dect-transceiver-list --name trx2 I see that slot0 is scanning:
DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0
in fact I forgot to bind trx1 and 2 to the cell… now I also see trx2 slot2 scanning (with a-crc-errors) but no result regarding the stations:
dect-transceiver-list --name trx2 DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 48 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 slot 1: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
On Aug 9, 2012, at 8:05 PM, Frédéric LECAILLE wrote:
if my analyze is correct, the virtual interface vtrx is scanning, not the physical one… as fat as I understand the command outputs…
On Aug 9, 2012, at 8:02 PM, Frédéric LECAILLE wrote:
On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote:
Updated patch attached <usdect.diff>
Ok thank you a lot Patrick.
Here are the results:
with your last patch:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
*The frequency is always 0 MHz*
The kernel logs seems to be OK:
[15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27
So I have tried your last patch with mine to force the rf_band to 1:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on...
About trx2:
dect-transceiver-list --name trx2 DECT Transceiver trx2: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0
slot 0: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
(no a-crc-errors)
If I remember well, with only my patch which forces the rf_band to 3 we got for trx2:
dect-transceiver-list --name trx2 I see that slot0 is scanning:
DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0
On Thu, 9 Aug 2012, Frédéric LECAILLE wrote:
On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote:
Updated patch attached <usdect.diff>
Ok thank you a lot Patrick.
Here are the results:
with your last patch:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
*The frequency is always 0 MHz*
The kernel logs seems to be OK:
[15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27
So I have tried your last patch with mine to force the rf_band to 1:
Right, it's supposed to be band 1.
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on...
Well, on vtrx you're not going to see stations unless you start some yourself.
is works Patrick…
dmesg |grep -v 'vtrx trx'
[23440.565272] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23441.095272] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23441.485276] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23441.915276] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23442.795285] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23443.105279] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23443.515292] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23444.685285] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23445.385285] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23446.125291] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23446.575290] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23447.025289] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23447.455291] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23448.355299] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23449.255298] page: RFPI: 37d08 bearer description: bt: 50000000 sn: 6 sp: 0 cn: 23
let me a few minutes to try to lock to the FP signal…
On Aug 9, 2012, at 9:18 PM, Patrick McHardy wrote:
On Thu, 9 Aug 2012, Frédéric LECAILLE wrote:
On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote:
Updated patch attached <usdect.diff>
Ok thank you a lot Patrick.
Here are the results:
with your last patch:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
*The frequency is always 0 MHz*
The kernel logs seems to be OK:
[15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27
So I have tried your last patch with mine to force the rf_band to 1:
Right, it's supposed to be band 1.
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on...
Well, on vtrx you're not going to see stations unless you start some yourself.
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…
On Aug 9, 2012, at 10:02 PM, Frédéric LECAILLE wrote:
is works Patrick…
dmesg |grep -v 'vtrx trx'
[23440.565272] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23441.095272] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23441.485276] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23441.915276] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23442.795285] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23443.105279] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23443.515292] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23444.685285] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23445.385285] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23446.125291] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23446.575290] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23447.025289] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23447.455291] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23448.355299] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [23449.255298] page: RFPI: 37d08 bearer description: bt: 50000000 sn: 6 sp: 0 cn: 23
let me a few minutes to try to lock to the FP signal…
On Aug 9, 2012, at 9:18 PM, Patrick McHardy wrote:
On Thu, 9 Aug 2012, Frédéric LECAILLE wrote:
On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote:
Updated patch attached <usdect.diff>
Ok thank you a lot Patrick.
Here are the results:
with your last patch:
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
*The frequency is always 0 MHz*
The kernel logs seems to be OK:
[15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27
So I have tried your last patch with mine to force the rf_band to 1:
Right, it's supposed to be band 1.
dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0
slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0
The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on...
Well, on vtrx you're not going to see stations unless you start some yourself.
On 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.
you meant I should set my cluster in PP mode and scan… I have already done that and I have never seen any information returned by dect-llme-scan even if the driver logs a lot of messages:
[26986.097752] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26986.407755] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26986.448471] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26986.937760] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26987.287762] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26987.348476] fixed part capabilities: fpc: 85110 hlc: ce30 [26987.737759] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26988.128476] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26988.598476] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26989.068476] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26989.457771] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26989.888477] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26990.237763] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26991.137771] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26991.198479] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26991.527775] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26991.548482] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26992.077772] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26992.528485] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26992.997781] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26993.038485] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26993.468485] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26993.777782] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26993.798483] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26994.227786] page: RFPI: 37d08 blind full slots: a8a [26994.617786] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26994.698489] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26995.228488] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26995.637791] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26996.428491] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26996.857795] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26997.877795] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26998.347802] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26998.368492] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26998.757811] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26998.798492] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [26999.127802] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [26999.577802] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27000.417806] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27000.438494] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27000.827804] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27001.318492] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27001.548495] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27001.938497] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27002.247813] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27002.308500] page: RFPI: d7ce8 bearer description: bt: 50000000 sn: 6 sp: 0 cn: 23 [27002.697809] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27003.087815] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27004.027819] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27004.068501] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27004.438502] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27004.748500] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27005.137827] identities information: e: 0 class: 0 emc: 21d5 fpn: 06fa1 rpn: 0 [27005.198504] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27005.648504] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 [27006.467829] multi-frame number: 7414440
On Aug 9, 2012, at 10:33 PM, Patrick McHardy wrote:
On 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.
-
Frédéric LECAILLE -
Patrick McHardy