Closed HelferP closed 1 year ago
Regarding the CPU frequency, add 1900 and other lists, otherwise after deleting these two, there will only be one 750. You check the list of settings of the original dtb of the Android factory, and submit it to the upstream kernel source code repo( https://github.com/unifreq/linux-5.15.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts ) after testing.
Firmware configuration changes can be submitted to https://github.com/ophub/firmware/tree/main/firmware/brcm
after deleting these two, there will only be one 750 But there are other frequencies in the compiled dtb, this is meson-sm1-h96-max-x3.dtb converted to dts. They are pulling up from somewhere else.
@HelferP 建议你在测试无线连接吞吐能力的时候,核对一下 修改前和修改后他们连接的频段是否在相同的频段,截图上看 433.3应该是5G单天线模式。117.0疑似连接到了2.4G,如果是2.4G单天线最大连接速率150Mbps。 可以通过指定ap的mac地址锁定 2.4G 或 5G频段。双频无线路由或AP他们2.4G和5G的mac地址是不同的。
修改前与修改后,处于相同的频段,测试的结果更为准确。
@HelferP 建议你在测试无线连接吞吐能力的时候,核对一下 修改前和修改后他们连接的频段是否在相同的频段,截图上看 433.3应该是5G单天线模式。117.0疑似连接到了2.4G,如果是2.4G单天线最大连接速率150Mbps。 可以通过指定ap的mac地址锁定 2.4G 或 5G频段。双频无线路由或AP他们2.4G和5G的mac地址是不同的。
My 2.4g and 5g access points have different ssids, so the box was definitely connected to 5G. I didn’t even connect to 2.4g, boxing doesn’t know its password.
非常好,这样很准确。 我正在参考你的 #850 尝试解决我遇到的 unaligned sg offset 3587, disabling descriptor DMA for transfer 还不知道他对无线传输有多少影响。
非常好,这样很准确。 我正在参考你的 #850 尝试解决我遇到的 unaligned sg offset 3587, disabling descriptor DMA for transfer 还不知道他对无线传输有多少影响。
Do you have the same box? Can you tell me more about "disabling descriptor DMA for transfer"
与你的盒子不同品牌,但SoC相同,无线部分不同。
我有两款S905X3的盒子,无线分别是 ap6255(bcm43455) 2.4G/150M, 5G/433M mt7661rsn(mt7663s) 2.4G/300M, 5G/867M
有关 disabling descriptor DMA for transfer 正准备尝试获得更多的相关内容。 待有一些进展,在分享上来。
settings of the original dtb of the Android factory I did the same as the original. It also does not have frequencies above 1.908 GHz.
You check the list of settings of the original dtb of the Android factory, and submit it to the upstream kernel source code repo( https://github.com/unifreq/linux-5.15.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts ) after testing.
Firmware configuration changes can be submitted to https://github.com/ophub/firmware/tree/main/firmware/brcm
I created a PR's for all.
The kernel repositories of the other two LTS are also updated, 5.4.y, 5.10.y and 6.1.y
https://github.com/unifreq/linux-5.4.y https://github.com/unifreq/linux-5.10.y https://github.com/unifreq/linux-6.1.y
Yes and for it I creates PRs
5.4.y, 5.10.y and 6.1.y
Thanks for sharing. Relevant modifications have been merged
In addition my issue https://github.com/ophub/amlogic-s9xxx-armbian/issues/850
I've been testing for several days on 5.15.86 with the changes made earlier and periodically getting the kernel panic again on reboot. I began to understand further and noticed that frequencies are registered in dtb, which are higher than those declared by the manufacturer. The maximum frequency declared by the manufacturer is -1.9 GHz. Therefore, I additionally turned off all the values that are higher, and in two weeks I never had a kernel panic.
Now about Wi-Fi. I replaced the contents of /lib/firmware/brcm/brcmfmac 4339-sdio.amlogic,sm1.txt. I didn't get the max real speed, but it's still more than double what it was before. There may be errors here, but this works for me:
Tests
Original brcmfmac 4339-sdio.amlogic,sm1.txt:
Edited brcmfmac 4339-sdio.amlogic,sm1.txt: