Skip to content

ipq8074: add Linksys MX5300 BDF #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 2 commits into from
Closed

ipq8074: add Linksys MX5300 BDF #23

wants to merge 2 commits into from

Conversation

testuser7
Copy link
Contributor

@testuser7 testuser7 commented Dec 8, 2023 •
edited
Loading

Add the BDF for Linksys MX5300.
IPQ8074 and QCA9984 BDF was edited to remove regdomain (country lock)
and update regdb.

@Ansuel
Copy link
Member

Ansuel commented Dec 9, 2023

@testuser7 what do you mean country locked?

@Ansuel
Copy link
Member

Ansuel commented Dec 9, 2023

Also one commit per BDF

@testuser7
Copy link
Contributor Author

@testuser7 what do you mean country locked?

https://forum.openwrt.org/t/adding-openwrt-support-for-linksys-mx5300/92667/36

@testuser7
Copy link
Contributor Author

Also one commit per BDF

Corrected.

@testuser7
Copy link
Contributor Author

BDF for the ath11k driver that can be found here has an external regdb (for qmi-board-id=255):

[
    {
        "board": [
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=528"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=528.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=529"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=529.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=531"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=531.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=534"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=534.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=656"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=656.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=657"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=657.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=658"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=658.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=659"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=659.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=660"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=660.bin"
            },
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=255"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=255.bin"
            }
        ],
        "regdb": [
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=255"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=255.regdb"
            }
        ]
    }
]

Does this mean that we can use an external regdb?

@testuser7
Copy link
Contributor Author

There is a problem with BDF for IPQ8074. Tx power is limited for ETSI countries. Example for GB:

root@OpenWrt:~# iwinfo phy1 txpowerlist
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
* 16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
  21 dBm ( 125 mW)
  22 dBm ( 158 mW)
  23 dBm ( 199 mW)

root@OpenWrt:~# iwinfo phy2 txpowerlist
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
* 15 dBm (  31 mW)
  16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)

Could this be related to the outdated regdb?

@ghost
Copy link

ghost commented Dec 18, 2023 •
edited by ghost
Loading

There is a problem with BDF for IPQ8074. Tx power is limited for ETSI countries. Example for GB:

root@OpenWrt:~# iwinfo phy1 txpowerlist
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
* 16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
  21 dBm ( 125 mW)
  22 dBm ( 158 mW)
  23 dBm ( 199 mW)

root@OpenWrt:~# iwinfo phy2 txpowerlist
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
* 15 dBm (  31 mW)
  16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)

Could this be related to the outdated regdb?

same issue on MX4200, region locked and GB suffers from this, best to use generic one, allows for higher power, it gets capped to 5dbm and on second 5ghz band gets capped to 8dbm

@testuser7
Copy link
Contributor Author

The same Tx power values for the ETSI region (GB country code) are observed in the vendor firmware:

~ # iwconfig ath1
ath1 IEEE 802.11axa ESSID:"_VelopSetupxxx"
           Mode:Master Frequency:5.22 GHz Access Point: xx:xx:xx:xx:xx:xx
           Bit Rate:2.4019Gb/s Tx-Power:16dBm
           RTS thr:off Fragment thr:off
           Encryption key:* Security mode:restricted
           Power Management:off
           Link Quality=0/94 Signal level=-93 dBm Noise level=-93 dBm
           Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
           Tx excessive retries:0 Invalid misc:0 Missed beacon:0

~ # iwconfig ath0
ath0      IEEE 802.11axg  ESSID:"_VelopSetupxxx"  
          Mode:Master  Frequency:2.447 GHz  Access Point: xx:xx:xx:xx:xx:xx   
          Bit Rate:573.5 Mb/s   Tx-Power:15 dBm   
          RTS thr:off   Fragment thr:off
          Encryption key:*   Security mode:restricted
          Power Management:off
          Link Quality=0/94  Signal level=-102 dBm  Noise level=-102 dBm
          Rx invalid nwid:131  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

There are probably hard limits set in the BDF file.

@testuser7 testuser7 mentioned this pull request Jan 31, 2024
Merged
@Razerwire
Copy link

Razerwire commented Feb 8, 2024 •
edited
Loading

The same Tx power values for the ETSI region (GB country code) are observed in the vendor firmware:
~ # iwconfig ath0

There are probably hard limits set in the BDF file.

@testuser7

I believe it might not be hard-coded (e.g. limited to 17dBm) by means of hardware.

I've been doing some further fiddling on my MX4200v1 and have phy2 working normally now:


ifindex 15
	wdev 0x200000004
	addr xx:xx:xx:xx
	ssid ProBeerenGiraffe
	type AP
	wiphy 2
	channel 100 (5500 MHz), width: 80 MHz, center1: 5530 MHz
	txpower 25.00 dBm
	multicast TXQ:
		qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
		0	0	139	0	0	0	0	23738		130

Phy2 is now working @ channel 100 / 5500mhz with TX power of 25dBm

(No weird - novel - hacks or altering regdb's needed):

phy#2 (self-managed)
country GB: DFS-ETSI

@Razerwire Razerwire mentioned this pull request Feb 12, 2024
Open
1 task
@testuser7 testuser7 mentioned this pull request Feb 15, 2024
Merged
@robimarko
Copy link
Contributor

@Ansuel You think this is ready to go?

@testuser7
ipq8074: add Linksys MX5300 BDF
8de82cc 
Add IPQ8074 BDF for Linksys MX5300.
BDF was edited to remove regdomain (country lock)
and update regdb.

Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
@testuser7
qca9984: add Linksys MX5300 BDF
745369d 
Add QCA9984 BDF for Linksys MX5300.
BDF was edited to remove regdomain.

Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
@robimarko
Copy link
Contributor

@testuser7 Are the issues mentioned in the comments resolved?

@testuser7
Copy link
Contributor Author

@testuser7 Are the issues mentioned in the comments resolved?

For the ETSI region, the tx power is still lower than allowed. But the exact same limits are in OEM firmware.
It seems to me that the limits in the BDF file are similar to those in the case of Dynalink DL-WRX36.

Apart from that, we have a fully functional BDF.

@robimarko
Copy link
Contributor

Merged, thanks.

@robimarko robimarko closed this Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@testuser7 @Ansuel @Razerwire @robimarko