-
Notifications
You must be signed in to change notification settings - Fork 87
ipq40xx: Add support for linksys MR6350 #24
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.
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
base: main
Are you sure you want to change the base?
Conversation
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. |
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. |
BDF files
|
Thansk for the hint, I removed the EU variant |
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. |
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) |
964c704
to
a7f7852
Compare
@Ansuel: Done and rebased |
Also drop the "variant=linksys-mr6350-fcc" -fcc from variant. |
I removed the variant from board.json and generated the bdf again. Can you please check if it has the expected format? |
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 Signed-off-by: Roland Reinl <[email protected]>
This does not look right to me:
First of all, why are there 2 BDF-s inside and second why is there no variant being set? |
@robimarko Maybe some github action should be implemented to check files? |
I dont know how one would do it, but it would be great to just have the info printed |
Mhhh an action might be interesting to implement... What info/checks should be done? |
Apart from displaying what is in the board file, I am thinking about an implementation that would return some basic information about BDF (version, regdb) to this tool: https://github.com/testuser7/ath_bdf_tool |
@robimarko: |
@Ansuel @robimarko Is there a way to distinguish QCA9888/QCA9984/IPQ4019 BDF files by content? |
@RolandoMagico This was done previously before you closed PR. |
Just add the missing variant in the |
@testuser7, @robimarko: Can you please help me with this PR?
What I execute:
What do I have to change to get what you need? |
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