nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: replace ar71xx occurences with ath79

Browse Source 
Replace occurences of ar71xx with ath79. Remove references of ar71xx
targets which are not relevant anymore.
This commit is contained in:
David Bauer 2021-06-26 02:20:04 +02:00
parent 9fdc57c175
commit f16061e021
4 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/dev/hardware.rst
View File

@ -34,8 +34,8 @@ The ``tiny`` device-class contains devices with the following limitations:
Adding profiles Adding profiles
--------------- ---------------
The vast majority of devices with ath9k WLAN is based on the ar71xx target of OpenWrt. The vast majority of devices with ath9k WLAN is based on the ath79 target of OpenWrt.
If the hardware you want to add support for is ar71xx, adding a new profile If the hardware you want to add support for is ath79, adding a new profile
is sufficient. is sufficient.
Profiles are defined in ``targets/*`` in a shell-based DSL (so common shell Profiles are defined in ``targets/*`` in a shell-based DSL (so common shell
@ -155,10 +155,7 @@ Build system support
'''''''''''''''''''' ''''''''''''''''''''
A definition for the new target must be created under ``targets``, and it must be added A definition for the new target must be created under ``targets``, and it must be added
to ``targets/targets.mk``. The ``GluonTarget`` macro takes one to three arguments: to ``targets/targets.mk``. The ``GluonTarget`` macro takes one to two arguments:
the target name, the Gluon subtarget name (if the target has subtargets), and the the target name and the OpenWrt subtarget name.
OpenWrt subtarget name (if it differs from the Gluon subtarget). The third argument
can be used to define multiple Gluon targets with different configuration for the
same OpenWrt target, like it is done for the ``ar71xx-tiny`` target.
After this, is should be sufficient to call ``make GLUON_TARGET=<target>`` to build the images for the new target. After this, is should be sufficient to call ``make GLUON_TARGET=<target>`` to build the images for the new target.

4
docs/features/autoupdater.rst
View File

@ -61,9 +61,9 @@ A fully automated nightly build could use the following commands:
git pull git pull
# git -C site pull # git -C site pull
make update make update
make clean GLUON_TARGET=ar71xx-generic make clean GLUON_TARGET=ath79-generic
NUM_CORES_PLUS_ONE=$(expr $(nproc) + 1) NUM_CORES_PLUS_ONE=$(expr $(nproc) + 1)
make -j$NUM_CORES_PLUS_ONE GLUON_TARGET=ar71xx-generic GLUON_RELEASE=$GLUON_RELEASE \ make -j$NUM_CORES_PLUS_ONE GLUON_TARGET=ath79-generic GLUON_RELEASE=$GLUON_RELEASE \
GLUON_AUTOUPDATER_BRANCH=experimental GLUON_AUTOUPDATER_ENABLED=1 GLUON_AUTOUPDATER_BRANCH=experimental GLUON_AUTOUPDATER_ENABLED=1
make manifest GLUON_RELEASE=$GLUON_RELEASE GLUON_AUTOUPDATER_BRANCH=experimental make manifest GLUON_RELEASE=$GLUON_RELEASE GLUON_AUTOUPDATER_BRANCH=experimental
contrib/sign.sh $SECRETKEY output/images/sysupgrade/experimental.manifest contrib/sign.sh $SECRETKEY output/images/sysupgrade/experimental.manifest

6
docs/user/getting_started.rst
View File

@ -84,14 +84,14 @@ Next go back to the top-level Gluon directory and build Gluon::
cd .. cd ..
make update # Get other repositories used by Gluon make update # Get other repositories used by Gluon
make GLUON_TARGET=ar71xx-generic # Build Gluon make GLUON_TARGET=ath79-generic # Build Gluon
In case of errors read the messages carefully and try to fix the stated issues In case of errors read the messages carefully and try to fix the stated issues
(e.g. install missing tools not available or look for Troubleshooting_ in the wiki. (e.g. install missing tools not available or look for Troubleshooting_ in the wiki.
.. _Troubleshooting: https://github.com/freifunk-gluon/gluon/wiki/Troubleshooting .. _Troubleshooting: https://github.com/freifunk-gluon/gluon/wiki/Troubleshooting
``ar71xx-generic`` is the most common target and will generate images for most of the supported hardware. ``ath79-generic`` is the most common target and will generate images for most of the supported hardware.
To see a complete list of supported targets, call ``make`` without setting ``GLUON_TARGET``. To see a complete list of supported targets, call ``make`` without setting ``GLUON_TARGET``.
To build all targets use a loop like this:: To build all targets use a loop like this::
@ -124,7 +124,7 @@ Cleaning the build tree
There are two levels of `make clean`:: There are two levels of `make clean`::
make clean GLUON_TARGET=ar71xx-generic make clean GLUON_TARGET=ath79-generic
will ensure all packages are rebuilt for a single target. This is usually not will ensure all packages are rebuilt for a single target. This is usually not
necessary, but may fix certain kinds of build failures. necessary, but may fix certain kinds of build failures.

2
docs/user/site.rst
View File

@ -102,7 +102,7 @@ opkg \: optional
- ``%d`` is replaced by the OpenWrt distribution name ("openwrt") - ``%d`` is replaced by the OpenWrt distribution name ("openwrt")
- ``%v`` is replaced by the OpenWrt version number (e.g. "17.01") - ``%v`` is replaced by the OpenWrt version number (e.g. "17.01")
- ``%S`` is replaced by the target board (e.g. "ar71xx/generic") - ``%S`` is replaced by the target board (e.g. "ath79/generic")
- ``%A`` is replaced by the target architecture (e.g. "mips_24kc") - ``%A`` is replaced by the target architecture (e.g. "mips_24kc")
- ``%GS`` is replaced by the Gluon site code (as specified in ``site.conf``) - ``%GS`` is replaced by the Gluon site code (as specified in ``site.conf``)
- ``%GV`` is replaced by the Gluon version - ``%GV`` is replaced by the Gluon version