From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] board: resurrect support for RIoTboard
Date: Mon, 10 Sep 2018 21:58:05 +0200 [thread overview]
Message-ID: <20180910215805.70aeb9ed@windsurf> (raw)
In-Reply-To: <20180908002452.11011-1-nikolay.dimitrov@retrohub.org>
Hello,
On Sat, 8 Sep 2018 03:24:52 +0300, Nikolay Dimitrov wrote:
> Resurrect support for RIoTboard after 2018.02.x deprecation.
>
> Signed-off-by: Nikolay Dimitrov <nikolay.dimitrov@retrohub.org>
> ---
> Changes v1 -> v2:
> - Add board's manufacturer website for more info
> - Switch to genimage sdcard image generation, update install steps in
> readme.txt
> - Switch from uImage to zImage
> - Switch rootfs to BR2_TARGET_ROOTFS_EXT2_4
> - Update u-boot to v2018.07
> - Update kernel to v4.18
> - Add myself in DEVELOPERS for riotboard
> ---
> DEVELOPERS | 4 +++
> board/embest/riotboard/genimage.cfg | 17 +++++++++
> board/embest/riotboard/readme.txt | 34 ++++++++++++++++++
> .../rootfs_overlay/boot/extlinux/extlinux.conf | 6 ++++
> configs/riotboard_defconfig | 41 ++++++++++++++++++++++
> 5 files changed, 102 insertions(+)
> create mode 100644 board/embest/riotboard/genimage.cfg
> create mode 100644 board/embest/riotboard/readme.txt
> create mode 100644 board/embest/riotboard/rootfs_overlay/boot/extlinux/extlinux.conf
> create mode 100644 configs/riotboard_defconfig
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-10 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 0:24 [Buildroot] [PATCH v2 1/1] board: resurrect support for RIoTboard Nikolay Dimitrov
2018-09-10 19:58 ` Thomas Petazzoni [this message]
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=20180910215805.70aeb9ed@windsurf \
--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.