summaryrefslogtreecommitdiff
path: root/configs/acmesystems_aria_g25_128mb_defconfig
AgeCommit message (Collapse)Author
2016-09-22configs/acmesystems_aria_g25: update and add genimage handlingBiagio Montaruli
- configs/acmesystems_aria_g25_128mb_defconfig, configs/acmesystems_aria_g25_256mb_defconfig : update default configuration files for both 128MB and 256MB version - board/acmesystems/aria-g25/genimage.cfg board/acmesystems/aria-g25/post-image.sh : add support for genimage in order to build sdcard.img - board/acmesystems/aria-g25/readme.txt : update documentation for Aria G25 and add notes about how to build sdcard.img Signed-off-by: Biagio Montaruli <biagio.hkr@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-05configs: Use HTTPS URL for Github reposPaul Cercueil
This makes it possible to clone git repositories hosted on Github while behind a firewall. Signed-off-by: Paul Cercueil <paul.cercueil@analog.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-05linux: use zImage by default on ARMThomas Petazzoni
Since quite some time, the kernel and bootloader communities consider zImage as the default format for kernel images on ARM, replacing uImage. The load address information in uImage is no longer needed, since the kernel is position-independent in terms of physical address, except on a few old platforms. For most people, using zImage is simply better/simpler, so let's switch to zImage as the default image format on ARM. All defconfigs are updated: 46 defconfigs no longer need to select explicitly zImage because it's the default, and 16 defconfigs now need to explicitly select uImage because that's no longer the default. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Matt Weber <matt@thewebers.ws> Acked-by: Julien Boibessot <julien.boibessot@armadeus.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-02-06defconfigs: all use the headers from the kernelYann E. MORIN
For most defconfigs, it was trivial to deduce the kernel version, by just reading the version string, which could be: - a standard upstream version string vX.Y.Z - a non-standard version string, but still containg the standard X.Y.Z Those for which it was not so trivial were those hosted on git tree. Since most were already using a custom linux-headers version, it could be easily deduced from that. It was confirmed by browsing said git trees and check the version there. There are a few cases were there was a mismatch: - microzed: uses a 3.18 kernel, but 3.8 headers; fixed. - xilinx_zc706: uses a 3.14 kernel, but 3.8 headers; fixed. - zedboard: uses a 3.18 kernel, but 3.8 headers; fixed. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-04configs/acmesystems_aria_g25: new configsGustavo Zacarias
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>