Support for Mikrotik LDF 5 ac

The Mikrotik LDF 5 ac (RBLDFG-5acD) is a device in the formfactor of a satellite dish feed (in sat tv called LNB) with a single Gigabit ethernet port with PoE and 5 GHz 802.11ac 2x2 MIMO single radio for bit rates up to MCS9 (867 Mbps). It can be combined with parabolic offset dishes of various size and gain to connect over large distances in point-to-point connections. See

The LDF 5 ac is ipq4018 based (quad core 32 bit ARM, 716 MHz) and comes with 256 MB RAM and 16 MB flash.

With the valued help of robimarko have created OpenWrt support for this device that can be tested here: (choose branch Mikrotik-LDF-5-ac).

Nice work @wwortel.

It would be really helpful if you rebased and squashed your commits. That way, one commit can show the device support being added. Then all you should need to get this added to OpenWrt is more in the commit message: device details and a signoff.

rebase example:
git switch Mikrotik-LDF-5-ac
git switch -c Mikrotik-LDF-5-ac-rebase
git rebase -i master

In the rebase -i editor, leave the first LDF-5-ac commit as pick, and change the rest of the LDF-5-ac commits pick into squash.
delete the lines for the commits that master will already have, but git should do this for you.
once you are happy & have tested the rebase, you can switch back to your main device branch, and reset --hard it to your rebase branch, then push --force this to github.

You can modify the last commit with git commit --amend

If the networking is similar to the SXTsq5ac's, you might need some extra settings to get VLANs (1 and 2 are usually problematic) working correctly with the Qualcomm driver.

thanks! Will give it a try.
in Mikrotik's original .dts qcom,phy_mdio_addr, qcom,poll_required, qcom,forced_speed, and qcom,forced_duplex are listed directly under edma@c080000. You put them under the &gmac subentries, one level lower. Is that intentional? Probably things that are not gmac specific but always applicable could be a level higher. Will the driver still find it when one shifts a .dts definition level up or down?

and also:
Mikrotik has two .dts entries under edma@c080000 that do not return in OpenWrt:
qcom,wan_port_id_mask = <0x10>; and
port_map = <0x04 0xffffffff>;

Would they only be needed in case of used of the switch and multiple ethernet ports?

Have tried these .dts mods but the 'LDF 5 ac' single ethernet port does not come up and the eth led stays off.

With single-phy, I think you will need to use ucidef_set_interface_lan "eth0"
If still no ethernet, you may need to change the phy_mdio_addr as well.

The differences to the Mikrotik OEM DTS: You are better off looking at OpenWrt device dts with single-phy, rather than the OEM DTS, as they use different drivers.
The OpenWrt ess-switch and ess-edma ipq40xx drivers are here

Qualcomm did not upstream these drivers, so vendors take QSDK ess-edma and ess-switch from some point in time and work from there.

Success! Needed in .dts to deactivate the switch, to add your suggestions, and to activate ess-psgmii.
Now OpenWrt boots with lan @ eth0. 02_network entry is now identical to that of sqtsq-5-ac2. Have updated github.
Will now try to read up on how to do this rebasing and squashing.
The one entry in your suggestion that I could not find in the drivers is phy-mode. It only gets parsed in the Distributed Switch Architecture driver, which appears not active here.