@Damirados At a quick glance, the repo you link is a hard fork from fariouche/rtl8812au-unified which is a soft fork of aircrack-ng/rtl8812au. Buildroot’s has a package for aircrack-ng/rtl8812au and since svpcom’s repo is also merging in upstream changes from fariouche’s repo, I see two options for you:

1. Generate a patch that captures the differences between svpcom and fariouche’s repo and add it to your patches/rtl8812au-aircrack-ng directory. This allows you to use the package available in upstream buildroot and also bring in all the code changes from svpcom in the form of a single or multiple patch files. More importantly, you don’t need to redefine a package. (This is the approach I would take long term)

NOTE: User defined packages can’t use existing names used by upstream packages.

2. Define a custom package by copying package/rtl8812au-aircrack-ng. Rename it. Modify RTL8821AU_SITE to point to svpcom repo and fix any compilation issues that might come up. This might be the easier option of the two approaches because generating a patch file might require dealing with conflicts.

Buildroot also has an alternative driver you might want to look at: package/rtl8821au

Once you have buildroot compiling your driver, you will need to enable it in the linux defconfig via make linux-menuconfig or by editing the system’s linux defconfig file directly.

I am currently building companion computer system for autonomous drones that enables live streaming.

As test drone I am using 5 inch FPV drone with flight controller capable of running ardupilot.

I am basically implementing OpenHD using nerves and membrane. So video transmission, bidirectional Mavlink and data tunnel over wifibroadcast

Once that is done I plan to experiment with features like object detection and tracking…

Thanks,

I found a package that is very similar to the one I am trying to compile, so I think it won’t be that hard using it as starting point.