This commit adds a new defconfig to build a X-based
graphical system for the Minnowboard MAX board.
* The 'openbox' windows manager is chosen because it's simple
and lightweigth.
* Basic X apps are enabled (such as xrandr, xterm), so we
can at least get a console and change video mode.
* ALSA default configuration is provided, so HDMI audio
works out-of-the-box.
* OpenGL is supported.
Tested on Minnoboard Turot (which is Minnowboard Max compatible).
[Peter: drop unneeded/specific toolchain config options]
Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Given Minnowboard and Minnowboard MAX boards are very similar,
it's desirable to unify the support for them.
This commit does the following:
1) Remove Minnowboard MAX's genimage.cfg, post-build.sh
and post-image.sh. These are identical to Minnowboard's.
2) Move Minnowboard MAX's linux config, and rename it.
It would be lovely to have a single kernel config file.
The kernel size penalty involved in adding support for
all the peripherals on both boards is small enough to
justify this.
However, the original Minnowboard has some GPIO buttons
that need to be registered by the kernel. This is not
upstreamed, and hence we need to use the yocto v3.8 kernel
to have this support.
3) Rename each grub config to grub-{board}.cfg.
4) Modify (the now unique) post-build script to use
a different grub config, according to the board.
5) Update both defconfigs, as per the above changes.
6) Finally, update the readme.txt.
[Peter: mention MAX in readme title]
Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Let's rework the board and config files to use genimage
to generate the SD card image directly.
Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Add noMMU configuration running on dc233c MMUv3 core with identity
memory map.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
dc232b is MMUv2 core, dc233c is very similar MMUv3 core. MMUv3 is the
latest full MMU for xtensa, which allows running both MMU and noMMU
linux variants.
Update configuration overlay and linux config file.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Tested-by: Waldemar Brodkorb <wbx@openadk.org>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
The current Buildroot defconfigs for Raspberry Pi and Raspberry Pi 2
instantiate a console on tty1, which appears on HDMI. Add a console on
the serial port (ttyAMA0) to be more consistent with other defconfigs
and provide a better out-of-the-box experience to users used to have a
serial console from Buildroot defconfigs.
This requires three changes:
1. have two 'console=' entries in the kernel command line: tty1,
then ttyAMA0;
2. change BR2_TARGET_GENERIC_GETTY_PORT to "console", so it starts
a getty on the last console= passed to the kernel, ttyAMA0;
3. add a new getty on tty1 to the generated inittab.
Step 2 is actually obtained by removing BR2_TARGET_GENERIC_GETTY_PORT
entirely from the defconfigs, since "console" is the default value.
Step 3 requires a post-build script since the Buildroot makefiles can
configure only one console.
Note: instead of simply adding a new getty on ttyAMA0 (which would
work) this patch actually changes BR2_TARGET_GENERIC_GETTY_PORT to
instantiate a console on UART, then adds back tty1 via
post-build.sh. This is done only to avoid the "GENERIC_SERIAL" comment
where we instantiate an HDMI console, then instantiate a really-serial
console on another line.
The result is these two inittab lines:
console::respawn:/sbin/getty -L console 0 vt100 # GENERIC_SERIAL
tty1::respawn:/sbin/getty -L tty1 0 vt100 # HDMI console
Cc: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle <arnout@mind.be>
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Similar to stm32f429_disco, this commit adds a configuration for the
Cortex-M4 based STM32F469 platform.
It requires a few kernel patches, which have already been submitted
upstream, as well as a small OpenOCD patch. Besides that, it re-uses
most of what has been added for the STM32F429 platform.
Signed-off-by: Lee Jones <lee.jones@linaro.org>
[Thomas:
- squash multiple patches from Lee Jones into one
- improve the readme.txt file
- sync the defconfig with the adaptations made to the stm32f429
configuration.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit adds a defconfig for the STM32F429 platform, which is
based on a Cortex-M4 core from ST Microelectronics. It is therefore
the first noMMU ARM platform supported in Buildroot.
This commit includes some files that will be common to several STM32
platforms (hence in board/stmicroelectronics) and some files that are
specific to the STM32F429 (hence in
board/stmicroelectronics/stm32f429-disco). More specifically, this
commit adds:
- A minimal Busybox configuration, which is small enough to boot
without causing OOM on such small noMMU platforms. The resulting
Busybox, statically linked with uClibc-ng, weights around 220
KB. For now, this file is located in board/stmicroelectronics/, but
we might consider moving it to package/busybox/ in the future if
needed.
- A post-build script that removes the mounting of /dev/pts (not
enabled in the kernel and not very useful for a system that has no
network and no X), and removes the network related init script and
configuration files (no network support).
- A flash.sh script, to perform the right OpenOCD invocations to
reflash the board.
- One small kernel patch to adjust the kernel command line in the
Device Tree, since it's the only way to do so.
- The usual readme.txt file.
Signed-off-by: Lee Jones <lee.jones@linaro.org>
[Thomas:
- squashed multiple patches from Lee Jones together
- added the minimal Busybox configuration
- added the post-build script
- improved the flashing script to not hardcode the location of the
output directory
- add the small kernel patch
- improve the readme.txt file
- test on HW the resulting image, after using the internal toolchain.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Use genimage to generate a sd card with a fat partition (at91bootstrap,
u-boot, kernel, dtbs) and an ext4 partition (rootfs).
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Use genimage to generate a sd card with a fat partition (at91bootstrap,
u-boot, kernel, dtbs) and an ext4 partition (rootfs).
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Use genimage to generate a sd card with a fat partition (at91bootstrap,
u-boot, kernel, dtbs) and an ext4 partition (rootfs).
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Let's rework the board and config files to use genimage
to generate the SD card image directly.
[Peter: add host-mtools for genimage vfat handling]
Signed-off-by: Ezequiel García <ezequiel@vanguardiasur.com.ar>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
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>
These three are Zynq boards and the build procedure is almost the
same. Having the SoC name prefix "zynq_" would be more consistent.
Also, this is the way in which the Linux Device Trees and the U-Boot
configuration files do.
This commit renames as follows:
zedboard_defconfig -> zynq_zed_defconfig
microzed_defconfig -> zynq_microzed_defconfig
xilinx_zc706_defconfig -> zynq_zc706_defconfig
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This defconfig allows to build all the components to boot from a sd card on a
SAMA5D2 Xplained board. For more details, please read the
board/atmel/readme.txt file.
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This variant of SAMA5D4 Xplained defconfig file allows to boot from a SD
card.
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
[Thomas: remove host-samba from the package selection, not needed when
booting from SD card.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Unify and update the defconfig files for Atmel Xplained boards:
- use at91bootstrap as first stage bootloader instead of u-boot spl
- build all dtb variants
- bump to linux4sam_5.2
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Ethernet is not working, but at least you get a shell and
can test applications for m68k.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.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>
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>
arm_versatile kernel defconfig updated to deal with multi-platform ARM
support and driver changes.
mips(el) 32-bits is back in working order for 4.5
Results table:
Defconfig Kernel Qemu Network Status
--------------------------------------------------------------
aarch64_virt 4.5 2.3.0 YES OK
arm_versatile 4.5 2.3.0 YES OK
arm_vexpress 4.5 2.3.0 YES OK
microblazebe 4.5 2.3.0 YES OK
microblazeel 4.5 2.3.0 YES OK
mips64el_malta 4.5 2.3.0 YES OK
mips64_malta 4.5 2.3.0 YES OK
mipsel_malta 4.5 2.3.0 YES OK
mips_malta 4.5 2.3.0 YES OK
ppc_g3beige 4.5 2.3.0 YES OK
ppc_mpc8544ds 4.5 2.3.0 YES OK
ppc_virtex_ml507 4.5 2.3.0 NO OK
ppc64_pseries 4.5 2.3.0 YES OK
sh4 4.5 2.3.0 YES OK
sh4eb 4.5 2.3.0 NO (1) OK
sparc_ss10 4.5 2.3.0 YES OK
sparc64_sun4u 4.5 2.3.0 YES OK
sparc_sun4u 4.5 2.3.0 YES OK
x86 4.5 2.3.0 YES OK
x86_64 4.5 2.3.0 YES OK
xtensa_lx60 4.4.5 2.3.0 YES (2) OK
(1) - Probably an endian issue with 8139 emulation/driver
(2) - xtensa ethernet broken in 4.5 so stick to 4.4.x
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
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>
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>
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>
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>
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>
* add a post-image.sh script
* update defconfig for genimage
* update readme.txt
[Peter: also add host-dosfstools dependency for vfat partition]
Signed-off-by: Phil Eichinger <phil@zankapfel.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Fixes:
https://travis-ci.org/buildroot/buildroot-defconfig-testing/jobs/114650744
git:// access to git.rocketboards.org has been failing for a while, and
git:// is sometimes not allowed through corporate firewalls, so change to
git-over-http instead.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Fixes:
https://travis-ci.org/buildroot/buildroot-defconfig-testing/jobs/114650743
git:// access to git.rocketboards.org has been failing for a while, and
git:// is sometimes not allowed through corporate firewalls, so change to
git-over-http instead.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
mxs-bootlets broke somewhere in between toolchain version bumps, leading to
boot failure.
Directly boot u-boot, as this is supported now, but it requires updated
partitioning (see readme.txt)
Drop mxs-bootlets patches, they aren't needed anymore.
Kernel is built as an uImage because the u-boot defconfig expects an
uImage on the second partition.
Tested on iMX233-OLinuXino-MINI hardware.
[Peter: adjust readme/config as suggested by Arnout]
Signed-off-by: Phil Eichinger <phil@zankapfel.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
It didn't make sense to keep the U-Boot scripts and post build/image
scripts under the nitrogen6x folder since they apply for all our
platforms.
Also update the readme.txt to make it clearer which defconfig should
be used depending on the platform targeted.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Bump to the latest kernel with DT path adjustment because Linux
commit ca5b34100c57 ("dts, arm64: Move dts files to vendor subdirs")
moved the DT file to the vendor sub-directory.
This commit was tested with the latest model (FVP v8 Foundation
Platform 9.5 build 41), so I updated the instruction in readme.txt
corresponding to it.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
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>
These defconfig options are set to their default values, so they are
redundant and can be removed without effect.
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
To allow a more complete "out-of-the-box" startup with the defconfig,
enable automatic network configuration of eth0 using DHCP.
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
