aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ar71xx/image/legacy.mk
Commit message (Collapse)AuthorAgeFilesLines
...
* ar71xx: fix legacy image buildingJo-Philipp Wich2016-06-241-20/+14
| | | | | | | | | | | | | | | | | | After the conversion from legacy device profiles to the newer profile information embedded in the image building code, the legacy recipes got triggered twice with different eval depths, leading to shell syntax errors when processing certain images. The double processing was caused by the remaining Image/Build macro in legacy.mk which serves as main entry point for the new style image build code in conjunction with the newly introduced LegacyDevice/* macros which caused the legacy image build fallback code to kick in. In order to fix the issue, rework all legacy macros to work under the legacy image build wrapper and remove the Image/Build macro of legacy.mk to prevent legacy profiles getting executed in the context of the new build code. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: merge profiles into image building codeJohn Crispin2016-06-221-0/+1
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: hiwifi-hc6361: lift size limit on kernel and rootfs partsYousong Zhou2016-06-221-19/+0
| | | | | | | | | | | | | | | | | | | | | | The patch has been run-tested and the relevant dmsg logs are as the following [ 0.762447] Creating 5 MTD partitions on "spi0.0": [ 0.767217] 0x000000000000-0x000000010000 : "u-boot" [ 0.775139] 0x000000010000-0x000000020000 : "bdinfo" [ 0.781014] 0x000000020000-0x000000fe0000 : "firmware" [ 0.810558] 2 uimage-fw partitions found on MTD device firmware [ 0.815043] 0x000000020000-0x000000170000 : "kernel" [ 0.821925] 0x000000170000-0x000000fe0000 : "rootfs" [ 0.827587] mtd: device 4 (rootfs) set to be root filesystem [ 0.831937] 1 squashfs-split partitions found on MTD device rootfs [ 0.837983] 0x0000005c0000-0x000000fe0000 : "rootfs_data" [ 0.845621] 0x000000fe0000-0x000000ff0000 : "backup" [ 0.851445] 0x000000ff0000-0x000001000000 : "art" While at it, convert to new build method Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* ar71xx: convert OM2P to device profileFelix Fietkau2016-06-071-0/+15
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: add WRTnode2Q supportKeLei Liang2016-06-061-0/+2
| | | | Signed-off-by: KeLei Liang <xzmu@wrtnode.com>
* ar71xx/image/edimax shorten the revision to 13 characterAlexander Couzens2016-06-011-2/+2
| | | | | | | edimax fails if the revision is longer than 13 characters. Also change the name from OpenWrt to LEDE Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* ar71xx: Generate sysupgrade images for OpenMesh devicesSven Eckelmann2016-05-231-0/+3
| | | | | | | | | | | | Some OpenWrt based firmwares like Gluon expect that a sysupgrade image exists when a device firmware can be updated via sysupgrade. This image wasn't created until now because OpenMesh devices use the same image for factory and sysupgrade flash. Copying the image from *factory.bin to *sysupgrade.bin is therefore enough to make the sysupgrade functionality visible. Reported-by: Matthias Schiffer <mschiffer@universe-factory.net> Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
* ar71xx: Add support for initramfs images for OpenMesh devicesSven Eckelmann2016-05-231-0/+1
| | | | Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
* ar71xx: split legacy image building code into a separate fileFelix Fietkau2016-05-231-0/+1210
Signed-off-by: Felix Fietkau <nbd@nbd.name>