aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot
Commit message (Collapse)AuthorAgeFilesLines
* uboot-envtools: add nsa325 envsAlberto Bursi2017-02-111-0/+1
| | | | | | adding nsa325 envs for consistency with other kirkwoods Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* uboot-kirkwood: fix goflexhome/net bootcommandAlberto Bursi2017-02-091-1/+1
| | | | | | | | | | Goflexhome/net use uImage, and to boot an uImage the u-boot must use bootm command, not bootz. Fixes the "i cannot boot LEDE with this u-boot" issue that I found out myself with my goflexnet. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* uboot-kirkwood: remove obsolete patchesAlberto Bursi2017-02-096-142/+0
| | | | | | | | | | all patches for CONFIG_SYS_GENERIC_BOARD are obsolete for uboot 2016 sources. Run-tested with the uboot of goflexnet, also the md5sum of all other uboots is the same with or without these patches. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* ixp4xx: put apex images into image staging directoryJo-Philipp Wich2017-01-271-1/+2
| | | | | | | | | | | | Do not put the apex images into the kernel build directory as this directory might get removed after kernel updates while the apex packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mxs: put u-boot images into image staging directoryJo-Philipp Wich2017-01-271-1/+2
| | | | | | | | | | | | Do not put the u-boot images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* oxnas: put u-boot images into image staging directoryJo-Philipp Wich2017-01-271-2/+2
| | | | | | | | | | | | Do not put the u-boot images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* sunxi: put u-boot images into image staging directoryJo-Philipp Wich2017-01-271-2/+3
| | | | | | | | | | | | Do not put the u-boot images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* layerscape: put u-boot and ucode images into image staging directoryJo-Philipp Wich2017-01-272-4/+6
| | | | | | | | | | | | Do not put the u-boot and ucode images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mvebu: put u-boot images into image staging directoryJo-Philipp Wich2017-01-271-2/+2
| | | | | | | | | | | | Do not put the u-boot images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing u-boot images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* uboot-lantiq: mark SPL variants as brokenMathias Kresin2017-01-251-0/+5
| | | | | | | | | | | | | | | | | All SPL variants are lzo compressed. The lzop binary is used for compression but is not available in tools. Additionally at least the NAND SPL support is broken and doesn't create working bootloaders. The fb3370 SPI NOR SPL enabled u-boot isn't required for LEDE since the LEDE images are targeting the pre-installed EVA bootloader. Mark these u-boot variants as well as the SPL variants for the reference boards as broken till the lzma issues are fixed upstream and we can use lzma instead of lzo compression. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-lantiq: fix a tool portability issueFelix Fietkau2017-01-251-3/+3
| | | | | | Use the standard off_t type instead of loff_t Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mxs: fix image build issuesFelix Fietkau2017-01-251-3/+7
| | | | | | | stage u-boot images in KERNEL_BUILD_DIR for building images always select uboot-mxs Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-envtools: add nsa310b envsAlberto Bursi2017-01-241-0/+1
| | | | | | | accessing the u-boot's envs on this device is required to read the mac address. These are the envs of the new u-boot, not of the stock one. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* uboot-zynq: switch to u-boot.mkFelix Fietkau2017-01-241-98/+17
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-sunxi: clean up, switch to u-boot.mkFelix Fietkau2017-01-242-74/+107
| | | | | | | | Instead of referencing u-boot packages from device profiles and having a -all metapackage, make the u-boot packages hidden (they don't install to bin/ anyway), and name the files in KERNEL_BUILD_DIR appropriately Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-pxa: remove packageFelix Fietkau2017-01-242-104/+0
| | | | | | support for pxa has been gone for a long time now Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-oxnas: switch to u-boot.mkFelix Fietkau2017-01-2429-76/+10
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-omap: switch to u-boot.mkFelix Fietkau2017-01-241-75/+16
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-mxs: switch to u-boot.mkFelix Fietkau2017-01-241-66/+10
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: switch to u-boot.mkFelix Fietkau2017-01-242-82/+12
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-layerscape-32b: simplify the package, it does not build anythingFelix Fietkau2017-01-241-64/+16
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-layerscape: switch to u-boot.mkFelix Fietkau2017-01-241-69/+22
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-imx6: switch to u-boot.mkFelix Fietkau2017-01-241-88/+29
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-at91: switch to u-boot.mkFelix Fietkau2017-01-241-71/+11
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-kirkwood: switch to u-boot.mkFelix Fietkau2017-01-241-78/+38
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-ar71xx: switch to using u-boot.mkFelix Fietkau2017-01-2415-74/+10
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-lantiq: switch to using u-boot.mkFelix Fietkau2017-01-241-259/+209
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-kirkwood: add uboot for nsa310bAlberto Bursi2017-01-243-9/+745
| | | | | | | | | | | | this commit allows to make a standalone u-boot for nsa310b. While both first-stage and second-stage u-boot work fine if installed to flash or loaded with kwboot, I could not get stock u-boot nor bodhi's u-boot to chainload any second stage u-boot (I also tried with dockstar's uboot that works fine on this device if loaded with kwboot). Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* packages: mark packages depending on a target as nonsharedMathias Kresin2017-01-243-0/+6
| | | | | | | | | The packages can't be build as shared packages due to the unmet dependencies. Fixes FS#418. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-lantiq: fix build issueFelix Fietkau2017-01-221-2/+3
| | | | | | | Do not reference BIN_DIR in the package install section directly, use $(1) instead. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: enable loader with the default profileFelix Fietkau2017-01-081-1/+1
| | | | | | Fixes build error Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-sunxi: enable parallel buildFelix Fietkau2017-01-051-0/+2
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-sunxi: add uboot-sunxi-all for selecting all other variantsYousong Zhou2017-01-051-142/+50
| | | | | | | | | While at it, the following changes are introduced - Rewrite the Makefile for better readability - Make parallel builds possible Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* uboot-lantiq: fix boot of images larger than 8MBMathias Kresin2017-01-0212-12/+36
| | | | | | | | Increasing CONFIG_SYS_BOOTM_LEN from 8 MB to 16 MB is necessary to support uncompressing images larger than 8 MB when using the bootm command. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-lantiq: fix build with gcc6Mathias Kresin2017-01-022-87/+852
| | | | | | | Backport u-boot commit 9b2c282b348dfe966bbba967dc7a45ce817cce50 to fix compile with gcc5 and gcc6. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: convert iconnect, ib62x0 and pogoplug_e02 to the new image build codeFelix Fietkau2016-12-244-34/+39
| | | | | | | Update the correspoding u-boot configs to stop relying on kernel-in-rootfs, which was removed a while back Signed-off-by: Felix Fietkau <nbd@nbd.name>
* treewide: clean up and unify PKG_VERSION for git based downloadsFelix Fietkau2016-12-223-12/+6
| | | | | | Also use default defintions for PKG_SOURCE_SUBDIR, PKG_SOURCE Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kexec-tools: remove useless CONFIG_KEXEC_TOOLS_TARGET_NAME indirectionFelix Fietkau2016-12-202-11/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kexec-tools: build by default, even if CONFIG_KERNEL_KEXEC is unsetFelix Fietkau2016-12-201-1/+1
| | | | | | | Helps find build issues and makes the package available on snapshot builds Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kexec-tools: enable support for x86_64Felix Fietkau2016-12-201-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kexec-tools: update to 2.0.14-rc1, fix build errorsFelix Fietkau2016-12-207-321/+24
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kexec-tools: fix compile errorGilles Mazoyer2016-12-201-0/+11
| | | | | | When compiling file vmcore-dmesg.c, several errors "unknown type name 'loff_t'" Signed-off-by: Gilles Mazoyer <mazoyer.gilles@omega.ovh>
* grub2: upgrade to 2.02-beta3 (3 years newer than previous)Alexandru Ardelean2016-12-204-50/+10
| | | | | | | | '100-musl-compat.patch' does not seem to be required anymore. '210-fix_serial_rtscts.patchi' is superseeded by: http://git.savannah.gnu.org/cgit/grub.git/commit/?id=bac5d1a64ab4191058a8fd4c05f6b3b339e249e7 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* grub2: disable 'check-macro-version' build rule in 'po' buildAlexandru Ardelean2016-12-201-0/+13
| | | | | | | | This seems to occur when gettext-full is built on the host-side and the autoreconf stuff re-generates some of the build files, except for the po/Makefile.in.in Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* grub2: do not generate mkfonts at build timeAlexandru Ardelean2016-12-201-0/+7
| | | | | | | | | | Even though these fonts may not be installed, they seem to be generated at build time. Seems that the configure script re-generated from configure.ac is a bit more annoying than it has to be. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* grub2: add PKG_FIXUP:=autoreconfAlexandru Ardelean2016-12-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reboot of: a0ea22ac430f91ab045431a79b2e2161e66cd56a Reverted: 3c52cbfa53056ded95ae5a7ae27319eafd5a37e5 The host-side build of grub2 requires this sometimes. This will re-generate the ./configure script from configure.ac. I don't know the conditions of how this reproduces, it just sometimes appears, and sometimes doesn't. Build error ``` <lede-dir>/build_dir/target-x86_64_musl-1.1.15_yogi/host/grub-2.02~beta2/build-aux/missing: line 81: aclocal-1.14: command not found WARNING: 'aclocal-1.14' is missing on your system. You should only need it if you modified 'acinclude.m4' or 'configure.ac' or m4 files included by 'configure.ac'. The 'aclocal' program is part of the GNU Automake package: <http://www.gnu.org/software/automake> It also requires GNU Autoconf, GNU m4 and Perl in order to run: <http://www.gnu.org/software/autoconf> <http://www.gnu.org/software/m4/> <http://www.perl.org/> Makefile:3962: recipe for target 'aclocal.m4' failed ``` Adding PKG_FIXUP adds sanity (i.e. autoreconf is used for host & target builds) over just using HOST_FIXUP. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* uboot-envtools: drop executable file attribute from files/ipqPiotr Dymacz2016-12-201-0/+0
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* uboot-envtools: fix Edimax BR-6425 board namePiotr Dymacz2016-12-201-1/+1
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* uboot-envtools: fix code formatting style in uci-defaults filesPiotr Dymacz2016-12-207-61/+62
| | | | | | | | | | Few minor code formatting style fixes, including: - keep one board per line - always use "|\" (for consistency) - remove redundant double quotes and empty lines Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* uboot-envtools: keep boards in alphabetical orderPiotr Dymacz2016-12-204-15/+15
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>