From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/olimex_a10_olinuxino_lime_defconfig: new board
Date: Mon, 2 Jul 2018 22:29:43 +0200 [thread overview]
Message-ID: <20180702222943.44eebe81@windsurf.home> (raw)
In-Reply-To: <1530543290-24202-1-git-send-email-leon.anavi@konsulko.com>
Hello,
On Mon, 2 Jul 2018 17:54:50 +0300, Leon Anavi wrote:
> Add a defconfig for the Olimex A10-OLinuXino-LIME, reusing most
> of the A20-OLinuXino-Lime and A13-OLinuXino files.
>
> The configurations for Olimex A10-OLinuXino-LIME feature:
> - U-Boot 2018.03
> - Mainline Linux kernel 4.14.26
>
> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Thanks for this contribution!
> board/olimex/a10_olinuxino/boot-mali.cmd | 5 +++
> board/olimex/a10_olinuxino/boot.cmd | 5 +++
> board/olimex/a10_olinuxino/genimage.cfg | 17 +++++++++
> board/olimex/a10_olinuxino/post-build.sh | 8 ++++
> board/olimex/a10_olinuxino/readme.txt | 57 +++++++++++++++++++++++++++++
> configs/olimex_a10_olinuxino_lime_defconfig | 48 ++++++++++++++++++++++++
You should add an entry in the DEVELOPERS file for this board (both for
the defconfig and the stuff in board/).
> diff --git a/board/olimex/a10_olinuxino/boot-mali.cmd b/board/olimex/a10_olinuxino/boot-mali.cmd
> new file mode 100644
> index 0000000..9fa5d65
> --- /dev/null
> +++ b/board/olimex/a10_olinuxino/boot-mali.cmd
> @@ -0,0 +1,5 @@
> +setenv bootm_boot_mode sec
> +setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait panic=10 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 consoleblank=0 ${extra}
> +ext4load mmc 0 0x43000000 /boot/script.bin
> +ext4load mmc 0 0x48000000 /boot/zImage
> +bootz 0x48000000
Where is this file being used ?
> diff --git a/board/olimex/a10_olinuxino/post-build.sh b/board/olimex/a10_olinuxino/post-build.sh
> new file mode 100755
> index 0000000..7a8a427
> --- /dev/null
> +++ b/board/olimex/a10_olinuxino/post-build.sh
> @@ -0,0 +1,8 @@
> +#!/bin/sh
> +
> +cp $BINARIES_DIR/boot.scr $TARGET_DIR/boot/boot.scr
> +
> +if [ -e $BINARIES_DIR/script.bin ]; then
> + # mali requires a legacy kernel
> + cp $BINARIES_DIR/script.bin $TARGET_DIR/boot/script.bin
It's a bit mysterious what is happening here. Where does this
script.bin file comes from ?
Besides those questions, looks good to me.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-02 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 14:54 [Buildroot] [PATCH] configs/olimex_a10_olinuxino_lime_defconfig: new board Leon Anavi
2018-07-02 20:29 ` Thomas Petazzoni [this message]
2018-07-05 7:31 ` Leon Anavi
-- strict thread matches above, loose matches on Subject: below --
2018-07-05 7:25 Leon Anavi
2018-07-05 7:37 ` Baruch Siach
2018-07-05 8:00 ` Leon Anavi
2018-07-05 7:58 Leon Anavi
2018-07-07 22:10 ` Arnout Vandecappelle
2018-07-09 13:49 ` Leon Anavi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180702222943.44eebe81@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.