From a functional perspective I fully agree...but from a software development perspective totally not. It has to do with the newly introduced wifi-qcom-ac driver.
It's still a little bit weird.
On the one hand, embedded development, as far as I know, is very frequently like that: you develop the whole system, and changing one little thing can force you to rewrite a lot of stuff if you want for it to work effectively.
On the other hand, however, RouterOS is, at least in its name, an operating system. With a lot of target architectures, that is. So its different components should theoretically be written in such a way that no component, except device drivers, is all-that dependent on the underlying hardware. The whole reason for drivers to exist in the first place is so that no other piece of software needs to be rewritten for everything to work with a new device.
My guess would be that WiFi 6 is just so radically different from WiFi 5 that it warranted new abstractions to be developed for efficient driver-software communication. And instead of doing a partial rewrite on the old CAPsMAN, someone at MikroTik decided "Screw it, let's do a full rewrite, it'll take the same amount of time".
Statistics: Posted by Nullcaller — Sun Jan 07, 2024 3:47 pm