aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu/image
Commit message (Collapse)AuthorAgeFilesLines
* mvebu: remove the clearfog-bundleFelix Fietkau2017-01-131-13/+1
| | | | | | It is obsoleted by proper SD card image support Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix image validation errorMathias Kresin2016-12-041-2/+2
| | | | | | | | The name from the Device define will be used in the metadata. Due to typo/different spelling, this name might not match the one exported in /lib/mvebu.sh. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: fix typo in image metadata supportMathias Kresin2016-11-271-2/+2
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: use image metadata for firmware validationFelix Fietkau2016-11-241-1/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add support for the Linksys WRT3200ACM (Rango)Imre Kaloz2016-10-241-1/+9
| | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mvebu: add sysupgrade support for clearfogJonas Gorski2016-09-261-1/+1
| | | | | | | | Add and enable sysupgrade support for clearfog boards, based on how the brcm2708 target does it. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add switch node to clearfogJonas Gorski2016-09-261-1/+1
| | | | | | | | Add a switch node to clearfog to probe and initialize it on Clearfog Pro. This make the switch work and allows using all six switch ports. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: make hidden and be m for clearfog to fix IB failing to add itJonas Gorski2016-09-261-1/+1
| | | | | | | | | | | | | Uboot-mvebu isn't a real package, which will break the image builder when it tries to install it during the packing step. Instead of cleafog selecting it through its default packages, make it default to m if the clearfog profile is selected. This will ensure it is always build, but never added to the rootfs. This fixes creating images for clearfog with IB. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: also install into KDIR to ensure it packaged in IBJonas Gorski2016-09-261-1/+1
| | | | | | | | The clearfog image requires u-boot, so package it into KDIR to make sure it is available in imageBuilder. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* image: remove padding parameter from append-kernel/append-rootfsMathias Kresin2016-09-131-2/+2
| | | | | | | | | | | Using pad-to instead of passing the optional padding to append-kernel or append-rootfs. It could be that the value of a variable is passed. In case the variable is empty no error is thrown. Furthermore the purpose of the extra parameter is hard to get without reading the code. Signed-off-by: Mathias Kresin <dev@kresin.me>
* image: add KERNEL_SIZE to the default device varsMathias Kresin2016-09-131-2/+0
| | | | | This reverts commit ec37a565878fd79d4127cbb843c17ce3b8dc97c0 and fixes the underlying issue.
* build: drop UBI EOF marker from images by defaultFelix Fietkau2016-09-121-0/+1
| | | | | | | | Only add them where they are actually required. Should help with compatibility issues with stock U-Boot images that access UBI Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix OpenBlocks AX3 imageMathias Kresin2016-09-111-1/+1
| | | | | | | | The KERNEL_SIZE variable is unset and no padding is applied. This looks like a typo to me since the ubinized image need to be aligned to the flash blocksize. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: use ext4/f2fs overlay filesystem for solidrun clearfogFelix Fietkau2016-09-102-14/+11
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: enable ext4, f2fs and loop device supportFelix Fietkau2016-09-101-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image: use k as unit suffix for blocksizeMathias Kresin2016-09-041-4/+4
| | | | | | | Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: use ptgen instead of fdisk to make the clearfog image script more ↵Felix Fietkau2016-09-021-55/+17
| | | | | | portable Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add sdcard image creation scriptJosua Mayer2016-09-023-2/+153
| | | | | | | | | | | | | | | | Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
* mvebu: clearfog: require uboot-mvebu-clearfogJosua Mayer2016-09-021-0/+1
| | | | | | | | | The u-boot variant for the clearfog is provided by the uboot-mvebu-clearfog, and not by the generic uboot-mvebu packae. Make sure the clearfog variant is selected when building for it. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: rework ClearFog bundle.tar.gz generationJo-Philipp Wich2016-08-141-12/+6
| | | | | | | Instead of introducing a fake filesystem type, move the tar generation step directly into the image build step. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mvebu: add ClearFog .tar.gz bundleJo-Philipp Wich2016-08-131-0/+26
| | | | | | | | | | The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* build: rename sysupgrade-nand to sysupgrade-tarJo-Philipp Wich2016-07-291-1/+1
| | | | | | | Now that the "sysupgrade-nand" step is used by non-NAND targets as well, rename it to "sysupgrade-tar" to make it more generic. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mvebu: limit image builds to profile selectionFelix Fietkau2016-07-261-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: switch to the new image build codeFelix Fietkau2016-07-211-229/+127
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix portability issues in the image makefile codeFelix Fietkau2016-05-201-5/+5
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add SolidRun ClearFog A1 supportLuka Perkov2016-02-171-0/+22
| | | | | | Signed-off-by: Andrej Vlasic <andrej.vlasic@sartura.hr> SVN-Revision: 48736
* mvebu: armada-385-rd has been renamed to armada-388-rd upstreamImre Kaloz2015-12-111-1/+1
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 47834
* mvebu: add support for the Linksys WRT1900ACS (Shelby)Imre Kaloz2015-10-081-0/+11
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 47164
* image.mk: move KDIR_TMP definition to a central locationJonas Gorski2015-08-141-4/+0
| | | | | | | | | | | Instead of each target defining it the same, move the KDIR_TMP definition to include/image.mk. In addition Image/Build/SysupgradeNAND already requires KDIR_TMP to be set, so it makes sense to have it globally defined. Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 46592
* image: fix jffs2(_nand) image generationJonas Gorski2015-08-051-1/+3
| | | | | | | | | | | | Variables dependend on JFFS2_BLOCKSIZE and NANDBLOCK_SIZE are used for template generation, so need to be present before inclusion of image.mk in target image Makefiles. So move all declarations to before any includes. Fixes: r42878 ("image.mk: clean up and parallelize mkfs calls") Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 46564
* mvebu: add support for the Linksys Caiman and CobraImre Kaloz2015-04-161-0/+22
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45456
* mvebu: copy the initramfs files to the bin dirImre Kaloz2015-04-131-2/+1
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45421
* mvebu: add comments to image generationImre Kaloz2015-04-131-0/+11
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45414
* mvebu: stop legacy image generationImre Kaloz2015-04-131-6/+0
| | | | | | | | If you can't find the firmware for you board, send proper patches. Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45413
* mvebu: generate a single firmware for the 385-db-apImre Kaloz2015-04-131-0/+9
| | | | | | | | This has been done without having a board, but should work. Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45412
* mvebu: migrate mamba support to the upstreamed codeImre Kaloz2015-04-121-5/+5
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45400
* mvebu: fix WRT1900AC ubinized imagesImre Kaloz2015-02-141-3/+4
| | | | | | | | | | The current pxa3xx_nand driver doesn't support sub-page writing, so the VID header offset must be specified explicitly. Signed-off-by: Claudio Leite <leitec@staticky.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44455
* mvebu: add note about the move to single firmware filesImre Kaloz2015-02-061-0/+3
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44291
* mvebu: support building images for a single boardImre Kaloz2015-02-061-3/+3
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44290
* mvebu: add Armada 385 DB AP supportImre Kaloz2015-02-051-0/+1
| | | | | | | Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44266
* mvebu: add the Armada 385 Reference Design supportImre Kaloz2015-02-051-0/+3
| | | | | | | Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44265
* mvebu: fix NAND and NOR optionsImre Kaloz2015-02-051-6/+10
| | | | | | | | | | | | | | | All the boards but Mamba had wrong UBI options so far, making it impossible to flash the built image on their respective storage medium. Fix all of the supported boards in order to make the generated images useful. Tested on a Mirabox, an Armada XP GP and an Openblocks AX3, and used the NAND chip datasheet for the others. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44264
* mvebu: add a subprofile for boards based on a small NORImre Kaloz2015-02-051-0/+25
| | | | | | | | | | | | | Some boards only come with a small NOR on it, where UBI isn't a good solution because of its overhead. Add a new subprofile for such boards, that rely on the mtd split framework instead. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44263
* mvebu: add large NOR sub-profile implementationImre Kaloz2015-02-051-0/+22
| | | | | | | | | | | While we supported only the NAND so far, some boards use a large enough NOR, where UBI is the only reasonable option. Create a new sub-profile template with a different set of UBI options. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44262
* mvebu: Add sub-profilesImre Kaloz2015-02-051-22/+74
| | | | | | | | | | | | | | In order to support the various board NAND layout that we support, introduce a sub-profile similar to the one used by ar71xx. These subprofiles provide a default implementation for most of the building functions, while allowing each sub-profile to override any of these operations in order to have a more specific behaviour, like Mamba expects for example. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44261
* mvebu: Switch to the generic mkuimage macroImre Kaloz2015-01-141-6/+3
| | | | | | | | | | | The mvebu image makefile define something almost identical to the generic implementation found in include/image.mk. Switch to this implementation. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> SVN-Revision: 43969
* mvebu: Replace the padjffs2 call by the generic definitionImre Kaloz2015-01-141-1/+1
| | | | | | | | | The mvebu image Makefile directly calls the padjffs2 utility, while there's an generic make function to do just that. Switch to it Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> SVN-Revision: 43968
* only call UbinizeImage and BuildSysUpgrade for boards we support them onImre Kaloz2014-12-261-2/+4
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 43779
* The ubinized filesystems should be used for generating the final images, so ↵Imre Kaloz2014-12-261-1/+1
| | | | | | | | store them in KDIR instead. Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 43778
* target/linux/*/image/Makefile: use new dts path variableJohn Crispin2014-07-211-1/+1
| | | | | | Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 41791
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 04:35:32 +0000