aboutsummaryrefslogtreecommitdiff
path: root/linux
Commit message (Collapse)AuthorAgeFilesLines
* rtai: remove option BR2_LINUX_KERNEL_EXT_RTAI_PATCHGravatar Thomas Petazzoni2015-04-222-17/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit removes BR2_LINUX_KERNEL_EXT_RTAI_PATCH because this option never worked. It was added in commit 8797a9cd1fe6723db34b0c125d0d9d04e3483e8d, which added package/rtai/ and RTAI as a Linux extension. The option prompt says "Path for RTAI patch file", so let's say you specify /home/foo/bar/myrtai.patch as the value for BR2_LINUX_KERNEL_EXT_RTAI_PATCH. Then the code does: RTAI_PATCH = $(call qstrip,$(BR2_LINUX_KERNEL_EXT_RTAI_PATCH)) and we have a package called 'rtai', so the normal logic of <pkg>_PATCH applies. Since the <pkg>_PATCH value does not contain ftp://, http:// or https://, the package infrastructure will try to download $(RTAI_SITE)/$(RTAI_PATCH), i.e: https://www.rtai.org/userfiles/downloads/RTAI/home/foo/bar/myrtai.patch Pretty clear that it has no chance of working. Now, let's assume an URL is used as the value of BR2_LINUX_KERNEL_EXT_RTAI_PATCH, such as http://foo.com/bar/myrtai.patch. In this case, it will be properly downloaded by the package infrastructure. But then, the following code kicks in: define RTAI_PREPARE_KERNEL $(APPLY_PATCHES) \ $(LINUX_DIR) \ $(dir $(RTAI_PATCH)) \ $(notdir $(RTAI_PATCH)) endef The value of $(dir $(RTAI_PATCH)) will be http://foo.com/bar/. How can $(APPLY_PATCHES) make use of such a stupid patch location? [Thomas: add Config.in.legacy handling, as suggested by Arnout, even if we believe that no-one could have ever used this option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* linux: Add uImage support for powerpc64Gravatar erico.nunes2015-04-141-2/+3
| | | | | | | | linux has uImage generation support for powerpc64 as well as powerpc, since 2.6.15. Signed-off-by: Erico Nunes <erico.nunes@datacom.ind.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: bump default to version 4.0Gravatar Gustavo Zacarias2015-04-131-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: fix fbtft kernel extensionGravatar Peter Seiderer2015-04-091-7/+7
| | | | | | | | | | | | | | | | Fixes fbtft kernel extension bug reported by Richard Fergusson ([1]): drivers/video/Kconfig:2525: can't open file "drivers/video/fbdev/fbtft/Kconfig" Fix: write the right fbtft/KConfig path to video/Kconfig or video/fbdev/Kconfig (instead of hard coded one) [1] http://lists.busybox.net/pipermail/buildroot/2015-January/117057.html Reported-by: Richard Fergusson <fergie4000@gmail.com> Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: migrate extensions to use the new infrastructureGravatar Yann E. MORIN2015-04-093-21/+3
| | | | | | Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: simplify adding new extensionsGravatar Yann E. MORIN2015-04-091-0/+7
| | | | | | | | | | | | | | | | | | | Curently, all three linux extensions follow the same layout: - test if the extension is enabled - add itself to linux' patch-dependencies - declare a macro, added as the pre-patch hook Except for the macro, all can be commonalised. Add a simple infrastructure for that: - extensions declare themselves in the list of extensions - extensions define their macro - the infra adds them to the patch-dependencies and pre-patch hooks as appropriate Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: fix extensionsGravatar Yann E. MORIN2015-04-093-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the move to the kconfig-package infra, linux extensions are broken. In our linux package, extensions are applied as pre-patch hooks. Before the kconfig-package infra, we had custom rules for the linux-*config targets, which were of the form: linux-menuconfig: linux-configure $(MAKE) -C $(LINUX_DIR) menuconfig This caused the linux tree to be fully configured before running the configurators, and thus linux dependencies were entirely fullfilled, and extensions were properly applied. Since we migrated (in dff25ea), the kconfig-package infra introduces a (hidden, internal) intermediate step 'kconfig-fixup' and decorelates the kconfig-part of the configuration from the actual package-part of the configuration: linux-configure -------> kconfig-fixup --> .config --> $(LINUX_CONFIG_FILE) / linux-menuconfig --' As thus, this (very useful!) use-case breaks (starting from a clean Buildroot tree): make menuconfig -> enable a kernel and at least one extension -> save and exit make linux-menuconfig -> extensions are not available Fix that by using the newly-introduced patch-dependencies, so that extensions are available before we try to patch the linux kernel. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Fix typos in comment blocksGravatar Masahiro Yamada2015-04-081-6/+6
| | | | | | | | | | | [Thomas: fix issues noticed by Arnout: - Rewrap the linux/Config.in paragraph - Revert the "is a toolchain dependency" -> "has a toolchain dependency" change from pkg-generic.mk, as the original was correct.] Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* packages: apply custom patches using *.patch instead of <pkg>-*.patchGravatar Thomas Petazzoni2015-04-062-2/+2
| | | | | | | | | | | | | | | | Several packages have some logic to apply custom patches that existed before the BR2_GLOBAL_PATCH_DIR mechanism: at91bootstrap, at91bootstrap3, barebox, uboot and linux. Currently, the logic of those packages to apply custom patches is to match <package-name>-*.patch, which is not consistent with what we've done for patches stored in the package directory, and for patches stored in BR2_GLOBAL_PATCH_DIR: in such cases, we simply apply *.patch. Therefore, for consistency reasons, this commit changes these packages to also apply *.patch. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* packages: indentation cleanupGravatar Jerzy Grzegorek2015-03-311-1/+1
| | | | | | | This commit doesn't touch infra packages. Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: use the package infrastructure to download patchesGravatar Thomas Petazzoni2015-03-301-17/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The linux package has a special handling of patches, with quite a bit of legacy in it. A problem caused by this special handling is that the linux package calls directly the DOWNLOAD_WGET macro, which means that the package infrastructure isn't aware of which patches get downloaded, and it prevents doing changes inside the package download infrastructure. This commit changes the handling of patches in the linux package in the following way: * The LINUX_PATCHES variable is kept as is: it lists all the patches mentioned in the Config.in option BR2_LINUX_KERNEL_PATCH. This option can contain http://, ftp://, https:// URLs, path to local files or local directories. This variable is *not* used by the generic package infrastructure, so it is purely internal to the Linux package. * The LINUX_PATCH variable is now filled in with the list of patches that should be downloaded. It is derived from LINUX_PATCHES by filtering the patches that have http://, ftp:// or https:// in their path. Since <pkg>_PATCH is handled by the package infrastructure, it means that those patches are now automatically downloaded and applied by the package infrastructure. * The LINUX_APPLY_PATCHES hook is renamed to LINUX_APPLY_LOCAL_PATCHES, because it is now only responsible of applying local patches: remote patches are handled by LINUX_PATCH. The implementation of the hook is changed to filter out the patches that have already taken care of by LINUX_PATCH, so that we only iterate through the list of local patches or local patch directories. [Thomas: adjust comment in the code according to Yann comments.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* linux-ext: update Xenomai help textGravatar Romain Naour2015-03-291-7/+15
| | | | | | | | | | Reword the help text and get ride of the supported kernel version list which is outdated since Xenomai version bump. [Thomas: rewrap text to the appropriate length, fix some typos.] Signed-off-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: bump default to version 3.19.3Gravatar Gustavo Zacarias2015-03-271-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: bump default to version 3.19.2Gravatar Gustavo Zacarias2015-03-191-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: stop if one linux patches doesn't applyGravatar Sébastien Szymanski2015-03-161-3/+3
| | | | | | | | | | If you have several linux patches directories, Buildroot does not stop if one patches of the first directories don't apply. This patch fixes this. Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: add note about why it's safe to include other .mk filesGravatar Yann E. MORIN2015-03-131-0/+8
| | | | | | | Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Remove trailing slash from all package site URLsGravatar Luca Ceresoli2015-03-101-1/+1
| | | | | | | | | The recommended form is without the trailing slash. Buildroot will add a slash between FOO_SITE and FOO_SOURCE as appropriate. Reported-by: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default to version 3.19.1Gravatar Gustavo Zacarias2015-03-081-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: clarify kernel configuration entriesGravatar Vivien Didelot2015-03-051-2/+5
| | | | | | | | | | | | | | Since BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE can either be a complete .config file or a defconfig file, it can be confusing to the user whether to choose BR2_LINUX_KERNEL_USE_DEFCONFIG or BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG. To avoid that confusion, clarify Kconfig entry messages for in-tree defconfig and custom (def)config files. Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux/linux.mk: custom dts path - build dtb only from *.dts filesGravatar Ivo Slanina2015-03-041-1/+5
| | | | | | | | | | | | | | | | | | When building device tree blobs from custom *.dts files, buildroot initializes KERNEL_DTS_NAME variable from all given file names. This causes that user can't provide one *.dts file and some other *.dtsi files as dependencies. Problem is fixed by adding filter for initializing KERNEL_DTS_NAME variable with *.dts files only. All user provided files are copied into kernel source tree, but only file names suffixed with *.dts are used for building appropriate *.dtb files. [Thomas: add comment into the code to explain why we are filtering .dts files only.] Signed-off-by: Ivo Slanina <ivo.slanina@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Merge branch 'next'Gravatar Peter Korsgaard2015-03-022-42/+20
|\ | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
| * linux: get rid of avr32 specificsGravatar Yann E. MORIN2015-02-142-5/+1
| | | | | | | | | | Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| * linux: avoid unnecessary changes in defconfig for INITRAMFS_SOURCEGravatar Thomas De Schampheleire2015-02-141-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When Buildroot is configured to append the root filesystem to the Linux kernel as initramfs, Buildroot sets the path to the initramfs source dynamically in the Linux configuration file. As this path is specified as an absolute path, typically being different for different users of the same project (e.g. containing a username), saving the configuration to a version control system (for example using 'make linux-update-defconfig') would result in a difference for this path at every invocation by a different user. Although this is technically not an issue, it is confusing that this generates a difference. Address this issue by using a not-yet-expanded make variable to specify the path to the initramfs source. That variable will be expanded by the Linux build system, which uses it both as a Makefile variable and a shell variable; thus, it needs to be specified in LINUX_MAKE_ENV (so it is exported and available in sub-processes of make). Any saved configuration file would simply contain the reference to the not-yet-expanded variable. As in the Linux build system, the config variables are both read from make as from a shell script, we cannot use $() syntax as this would be interpreted as a command invocation by the shell. Instead, use ${} syntax which is interpreted as variable reference both by the shell as by make. [Thomas: - Really make the patch work by using $(LINUX_MAKE_ENV) instead of $(TARGET_MAKE_ENV). Otherwise, the new BR2_BINARIES_DIR variable is not passed at all stages of the build process, which makes the build fail when an initramfs is used.] Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: "Yann E. Morin" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| * linux: migrate to the kconfig infrastructureGravatar Thomas De Schampheleire2015-02-141-28/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | Migrate the linux package to the kconfig infrastructure. A notable change compared to the original behavior: - the targets linux-update-(def)config are now always saving the config file, even for a defconfig bundled in the linux sources. This is done to keep the kconfig infrastructure simple. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: "Yann E. Morin" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| * linux: qstrip the path to the custom configuration fileGravatar Thomas De Schampheleire2015-02-141-1/+1
| | | | | | | | | | | | | | | | | | | | Even though this is not strictly necessary with the current version of linux.mk, it becomes necessary when migrating linux.mk to the kconfig infrastructure. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: "Yann E. Morin" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| * linux: bump default to version 3.19Gravatar Peter Korsgaard2015-02-091-2/+2
| | | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* | linux: add support for 4.x versionsGravatar Sébastien Szymanski2015-02-271-2/+4
|/ | | | | Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default to version 3.18.6Gravatar Peter Korsgaard2015-02-061-2/+2
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default to version 3.18.5Gravatar Gustavo Zacarias2015-01-311-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default to version 3.18.4Gravatar Gustavo Zacarias2015-01-271-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default to version 3.18.3Gravatar Gustavo Zacarias2015-01-161-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: clarify help text for 'custom tarball'Gravatar Thomas De Schampheleire2015-01-161-2/+7
| | | | | | | | | | | | The help text for Linux option 'Custom tarball' only refers to ftp or http tarballs, while in reality file or scp protocols are also supported. Triggered by a recent support question, update the help text to clarify this. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux/linux.mk: fixed downloading kernel patchesGravatar Ivo Slanina2015-01-141-1/+1
| | | | | | | | | | | | | | | Patches located at ftp or http(s) URLs were downloaded using DOWNLOAD macro. For example, if linux source was located at external git repository, DOWNLOAD macro uses git scheme as well and buildroot tried to downlod a path using DOWNLOAD_GIT macro. As a result, nothing was downloaded and build siletly passes. Patches located at mentioned URLs is now downloaded directly with DOWNLOAD_WGET macro. Signed-off-by: Ivo Slanina <ivo.slanina@gmail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux/linux.mk: added https:// pattern for kernel patchesGravatar Ivo Slanina2015-01-141-2/+2
| | | | | | | | | | | Patches located at https:// scheme URL were threated as directories, causing build failures. Fixed by adding https:// pattern. Signed-off-by: Ivo Slanina <ivo.slanina@gmail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* xtables-addons: enable necessary kernel optionsGravatar Gustavo Zacarias2015-01-101-0/+3
| | | | | | | | | | Enable the required conntrack/netfilter options, otherwise xtables-addons will fail to build. The basic iptables options are already covered by the iptables package which is a required dependency anyway. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* iptables: enable basic kernel optionsGravatar Gustavo Zacarias2015-01-101-0/+5
| | | | | | | | Enable the basic kernel options for iptables to be useful at least to filter incoming connections. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: add fbtft kernel extensionGravatar Peter Seiderer2015-01-102-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Tested with RaspberryPi B+ and PiTFT Mini Kit - 320x240 2.8" TFT (see [1] and [2]) and the following target configuration changes: - cmdline.txt: add 'fbcon=map:10 fbcon=font:VGA8x8' - add /etc/modules-load.d/fbtft.conf with 'fbtft_device' - add /etc/modprobe.d/00-fbtft.conf with 'options fbtft_device name=adafruit28 rotate=90 gpios=dc:25' [1] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9893.jpg [2] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9897.jpg [Thomas: - Rename prompt of the Linux extension to "FB TFT drivers" - Remove the full name of the kernel config options in the help text. Giving their CONFIG_<foo> name is enough. - Remove the mention of CONFIG_SPI_BCM2708, since this makes the description RaspberryPi specific, while these drivers can work with any SPI controller. - Refactor the code in linux-ext-fbtft.mk to avoid duplication between the < 3.15 and >= 3.15 cases. - Make the fbtft package a promptless package, since there is no point in selecting only this package, without the kernel extension. - Change the license to GPLv2, since it's kernel code.] Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: bump default to version 3.18.2Gravatar Gustavo Zacarias2015-01-091-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: hide custom patches when using a local treeGravatar Vivien Didelot2015-01-071-0/+1
| | | | | | | | | | When using a custom local tree, we're using the OVERRIDE_SRCDIR internally, which means we do not apply patches. Since this is the expected behavior, make BR2_LINUX_KERNEL_PATCH and BR2_LINUX_KERNEL_CUSTOM_LOCAL options exclusive. Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: change Device Tree promptGravatar Yann E. MORIN2015-01-021-3/+3
| | | | | | | | | | | | | | | | | The current prompt seems to imply that we want to add Device Tree support to the Linux kernel: [*] Device tree support But what it really means is that Buildroot will build a DTB. Change the prompt so that it is obvious that this is the intended behaviour, and users do not get mislead as to why Device Tree support is not automatically added to their Linux kernel. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: fix breakage from d4b2b032a00c9922c9efa144b014dc086a7e48f1Gravatar Gustavo Zacarias2014-12-241-0/+2
| | | | | | | | | | Unbreak qemu_xtensa_lx60_defconfig where LINUX_IMAGE_NAME != LINUX_TARGET_NAME. It incorrectly overwrites LINUX_IMAGE_NAME even if it was set before, defeating the purpose of IMAGE being different than TARGET. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: bump default to version 3.18.1Gravatar Gustavo Zacarias2014-12-161-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: fix recursively defined variableGravatar Yann E. MORIN2014-12-151-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When running 'make printvars', the output stops at the time we dump the Linux related variables, with: linux/linux.mk:109: *** Recursive variable `LINUX_TARGET_NAME' references itself (eventually). Stop. And that's expected, since we have: 109 LINUX_TARGET_NAME = $(LINUX_IMAGE_NAME) [...] 112 ifeq ($(LINUX_IMAGE_NAME),) 113 LINUX_IMAGE_NAME = $(LINUX_TARGET_NAME) 114 endif Even though they are defined in a way that ensures they are in fact not recursively defined (the if-block ensures that), 'printvars' does dump all our variables by evaluating all of them, which in that specific case implies they are recursively defined. Fix that by explicitly setting LINUX_IMAGE_NAME in each if-block. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default to version 3.18Gravatar Gustavo Zacarias2014-12-081-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default version to 3.17.6Gravatar Gustavo Zacarias2014-12-081-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: bump default version to 3.17.4Gravatar Gustavo Zacarias2014-11-211-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default version to 3.17.3Gravatar Gustavo Zacarias2014-11-161-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump default version to 3.17.2Gravatar Gustavo Zacarias2014-10-301-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package: indentation cleanupGravatar Jerzy Grzegorek2014-10-261-4/+4
| | | | | Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* apply-patches.sh: Use the "APPLY_PATCHES" variable to call the scriptGravatar Fabio Porcedda2014-10-252-5/+5
| | | | | | | | | | To easy up adding optional parameters when calling the "apply-patches.sh" add and use the "APPLY_PATCHES" variable to execute the script. Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>