Adding OpenWrt support for Xiaomi AX3600 (Part 1)

Done, Dynalink is part of robimarkos PR branch

3 Likes

Can somebody share the IRQ balancing script, I want to include it as part of the target.

I believe this is the script that @dchard posted

#assign 4 rx interrupts to each cores
echo 8 > /proc/irq/50/smp_affinity
echo 4 > /proc/irq/51/smp_affinity
echo 2 > /proc/irq/52/smp_affinity
echo 1 > /proc/irq/53/smp_affinity

#assign 3 tcl completions to 3 CPUs
echo 4 > /proc/irq/73/smp_affinity
echo 2 > /proc/irq/74/smp_affinity
echo 1 > /proc/irq/75/smp_affinity

@robimarko news for the single Fw on ax3600?

None, havent looked at it, was busy rebasing and sending all of the stuff that was partially reviewed again to try and get it into 6.1

2 Likes

So you didn't watch my ELC talk? :disappointed_relieved:

2 Likes

Nope, barely got any time to watch the conferences.
Is it public?

Full ELC Playlist:

4 Likes

Thanks, will give it a go over the weekend.

1 Like

I have opened a tracking issue for PR blockers:

If you think I missed something, please comment.

@sumo They seriously posted 360p recording

7 Likes

@robimarko Seems you didn't enable WolfSSL CPU crypto instructions in your build profile.

It was the default until recently

Okay, I see. :slight_smile:

The next question is how to enable the neon version of wolfssl?
(BTW, I only changed "CONFIG_WOLFSSL_HAS_CPU_CRYPTO" to "y".)

That will enable the use of crypto extensions I dont know about anything else, though NEON should pretty much always be enabled as its part of ARMv8 and not optional AFAIK.

I have confusion on /proc/crypto, even I turn on CPU crypto, I didn't get the "neon" result.
image

That is kernel crypto, NEON is enabled for algos that support it.

Thanks for your answer. :smile:

Unfortunately the firmware version 2.7.0.1-01744 is still crashing under certain conditions, even on the Dynalink :roll_eyes:

@dchard did you succeed in the end with this version?

If yes, I suggest updating because the current version does have crashed as well…. So hopefully less crashes is better :slight_smile:

No. I repacked the BDF to match the one expected by my AX6, but it crashes instantly on load the same way as with the original AX6. I did not have the time to analyze the cal file sent by Kirdes, if there is any difference there.

Non the less the fact it works at least the same according to Kirdes, points us towards either the BDF or the CAL file, as the driver is the same.