123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384 |
- Adding support for new hardware
- ===============================
- This page will give a short overview on how to add support
- for new hardware to Gluon.
- Hardware requirements
- Having an ath9k (or ath10k) based WLAN adapter is highly recommended,
- although other chipsets may also work. VAP (multiple SSID) support
- is a requirement. At the moment, Gluon's scripts can't handle devices
- without WLAN adapters (although such environments may also be interesting,
- e.g. for automated testing in virtual machines).
- .. _hardware-adding-profiles:
- Adding profiles
- The vast majority of devices with ath9k WLAN uses the ar71xx target of OpenWrt.
- If the hardware you want to add support for is also ar71xx, adding a new profile
- is enough.
- Profiles are defined in ``targets/<target>-<subtarget>/profiles.mk``. There are two macros
- used to define which images are generated: ``GluonProfile`` and ``GluonModel``. The following examples
- are taken from ``profiles.mk`` of the ``ar71xx-generic`` target::
- $(eval $(call GluonProfile,TLWR1043))
- $(eval $(call GluonModel,TLWR1043,tl-wr1043nd-v1-squashfs,tp-link-tl-wr1043n-nd-v1))
- $(eval $(call GluonModel,TLWR1043,tl-wr1043nd-v2-squashfs,tp-link-tl-wr1043n-nd-v2))
- The ``GluonProfile`` macro takes at least one parameter, the profile name as it is
- defined in the Makefiles of OpenWrt (``openwrt/target/linux/<target>/<subtarget>/profiles
|