Following what's done in Raspberry Pi's defconfigs, let's
unify the consoles in Minnowboard Max defconfigs, providing
consoles on HDMI and serial port.
[Peter: use tty1 like on rpi]
Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Also, rebase kernel config and adapt kernel command line in grub config file
to follow mmc numbering change.
[Peter: drop now unused linux-4.4.config]
Signed-off-by: Vincent Stehlé <vincent.stehle@intel.com>
Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Peter Korsgaard <peter@korsgaard.com>
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.
[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>
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>
Very similar to the older Minnowboard, except that it works with mainline
Linux, uses 64bit firmware and a realtek NIC needing firmware.
The Linux configuration is based on the configuration fragment on elinux:
http://elinux.org/Minnowboard:MinnowMaxLinuxKernel
Many thanks to Circuitco for sponsoring a board.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
