The recent change to default to gcc 6 for the internal toolchain broke this
defconfig as the u-boot doesn't contain commit 9b2c282b34 (compiler*.h: sync
include/linux/compiler*.h with Linux 4.5-rc6) which was added during the
2016.03 cycle.
Fix the build by bumping u-boot to 2017.05.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
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>
Notice: We cannot move to u-boot 2016.03 without changing the boot setup as
2016.03 broke legacy boot on omap4.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Now that we have modules (including usb/net) loaded automatically, we can
enable dhcp on eth0.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
The omap2plus kernel defconfig builds most drivers as modules, so we need
(automatic) module loading to be able to use usb/display/..
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
The genimage configuration creates a vfat filesystem, so ensure we have
dosfstools / mtools built for the host.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
VFPv3 and NEON was enabled and a readme.txt file was added.
Fixes bug #7580.
Tested on Pandaboard ES.
[Peter: use EABIhf]
Signed-off-by: Sergio Prado <sergio.prado@e-labworks.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
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>
Gcc 4.6.x is legacy now; remove version specification from the config file to
repair the build.
Signed-off-by: Vincent Stehlé <vincent.stehle@laposte.net>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Since commit 2a5cf5e (check kernel headers version), we also need to
specify the series of the custom kernel headers version.
The defconfigs file that define such a custom kernel headers version
now fail to build.
Add the required _AT_LEAST_X_Y options to those config files. Done with
this (convoluted but very fast, uch faster ythan manual editing!) rule:
for f in $( git grep -l BR2_DEFAULT_KERNEL_VERSION=\"3 ); do
grep -E '^BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_' "${f}" >/dev/null && continue
sed -r -e '/^(BR2_DEFAULT_KERNEL_VERSION="3\.([[:digit:]]+).*")$/s//\1\nBR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_\2=y/' "${f}"
done
Only kernels >= 3.0 need those options in the defconfig, since the
default for 2.6.x kernels is correct (selects _AT_LEAST_2_6), and
the default is not saved in a defconfig.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
The patch "pandaboard: Fix defconfig build" locked the
default pandaboard kernel to 3.8.11. This is inconvenient,
since the boot process has changed since kernel > 3.8.
Update the default kernel to 3.12.2 and fix the boot image
configuration, but remain compatible with legacy U-Boot
versions by using appended flattened device tree uImage.
This change *should* keep future kernels compatible with a
fixed U-Boot version.
Note the default device tree is now for the pandaboard-ES,
so users of other board revisions will need to set the
correct DTS_NAME.
[Peter: use custom kernel headers version (3.12.2)]
Signed-off-by: Thomas Pedersen <thomas@cozybit.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Commit 75b7dc68 ("linux: default to 3.9, remove 3.8") made 3.9 the
default kernel version.
The omap kernel switched to multiplatform kernel during the 3.9 kernel
development cycle. Obviously, the uImage generation doesn't work anymore
with multiplatform kernels, since you have to provide the kernel load
address, resulting in a build error.
Lock down the kernel version to 3.8 to keep the old behaviour until
someone submits a patch to switch to multiplatform kernel.
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This is a default configuration for Panda and PandaES, tested on both
platforms.
DEVTMPFS is enabled, to use static dev configuration one would need
to update the generic dev table for ttyO driver.
Panda is well supported in mainline kernel with omap2plus_defconfig,
so this should be safe.
U-boot SPL support is enabled by default as x-loader is now
deprecated.
With OMAP platforms u-boot,img format is prefered now, so it's enabled
by default as well. Also, on PandaBoard, the name of SPL target file
is MLO.
Signed-off-by: Nicolas Dechesne <n-dechesne@ti.com>
Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
