ipq40xx: Add support for linksys MR6350

[RolandoMagico]

Extracted from FW_MR6350_1.1.3.210129_prod.img and repacked.
It's containing only the settings for FCC. EU is identical to FCC.

MD5: 673a0d9f1508f5b6943ceb2ee64f64c8
SHA256: f6197c9e6f28ee0192f3e182b3543ab67209109d29bc493793044231381ce6a3

Based on the thread https://forum.openwrt.org/t/howto-create-ipq40xx-bdf-files

PR adding the device: openwrt/openwrt#14098

[testuser7]

How are BDF files selected?

[RolandoMagico]

How are BDF files selected?

Hi @testuser7, that's the first time I tried to create BDF files so I don't have detailled background regarding this topic. Can you please give me some more background regarding your question?

Update: No clear if it answers your question: The BDF contains the data for the main areas. I also checked if there is already a file with the same MD5 in this repository, there isn't.
The file is required for openwrt/openwrt#14098 and is referenced in t the devlice DTS (see https://github.com/openwrt/openwrt/pull/14098/files#diff-12d25e8195d7707e624211ad97b60f2f75c3041cef9c44bdd4f182902b463a93, line 86 and line 91.

[testuser7]

How are BDF files selected?

Hi @testuser7, that's the first time I tried to create BDF files so I don't have detailled background regarding this topic. Can you please give me some more background regarding your question?

I'm not sure if additional BDF files will be used. Currently, there is no mechanism that would allow you to set another variant from the system level.

[RolandoMagico]

I'm not sure if additional BDF files will be used. Currently, there is no mechanism that would allow you to set another variant from the system level.

Right, as far as I understood from this post, additional BDFs are only included to give "power users" the ability to change them.

[testuser7]

Right, as far as I understood from this post, additional BDFs are only included to give "power users" the ability to change them.

BDF files fcc and eum just have different country code and checksum. Otherwise they are identical.

0x833A - GB
0x8348 - US

OFFSET      bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-mr6350-eum.bin   bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-mr6350-fcc.bin
--------------------------------------------------------------------------------
0x00000000  20 2F 0D 14 01 01 00 03 7F 12 34 56 3A 83 00 00 |./........4V:...| \ 20 2F 7F 14 01 01 00 03 7F 12 34 56 48 83 00 00 |./........4VH...|
*

OFFSET      bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-mr6350-eum.bin   bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-mr6350-fcc.bin
--------------------------------------------------------------------------------
0x00000000  20 2F 28 64 01 01 12 34 56 78 90 12 3A 83 00 00 |./(d...4Vx..:...| \ 20 2F 5A 64 01 01 12 34 56 78 90 12 48 83 00 00 |./Zd...4Vx..H...|
*

[RolandoMagico]

BDF files fcc and eum just have different country code and checksum. Otherwise they are identical.

Thansk for the hint, I removed the EU variant

[Ansuel]

any news on this? can someone summarize the situation?

[RolandoMagico]

any news on this? can someone summarize the situation?

Hello, This is the first time I created BDF files, but from my point of view nothing else has to be done here. I tested the files with MR6350 and they worked.
If there is anything missing, please tell me and I’ll fix it

[Ansuel]

Honestly I would just include the fcc and remove the tag from the variant. @RolandoMagico can you do that?

Unless you notice big performance degradation, we should stick to the most compatible one across regions (that is FCC)

[RolandoMagico]

@RolandoMagico can you do that?

@Ansuel: Done and rebased

[Ansuel]

Also drop the "variant=linksys-mr6350-fcc" -fcc from variant.