From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] board: Add a readme file for Toradex Colibri Vybrid module
Date: Tue, 31 May 2016 23:23:42 +0200 [thread overview]
Message-ID: <20160531232342.556583b8@free-electrons.com> (raw)
In-Reply-To: <3aa77fd453222598bc4af73a2fed155f68459738.1449902276.git.maitysanchayan@gmail.com>
Hello,
On Sat, 12 Dec 2015 12:36:58 +0530, Sanchayan Maity wrote:
> Add a readme file documenting how to use the build output images
> using and cross referencing the update procedure as used by Toradex.
This patch should be squashed/merged into your previous patch. I.e, we
want a single patch adding the defconfig/readme for the Toradex Colibri
Vybrid module.
We also need your Signed-off-by here.
> ---
> board/toradex/colibri-vf/readme.txt | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
> create mode 100644 board/toradex/colibri-vf/readme.txt
>
> diff --git a/board/toradex/colibri-vf/readme.txt b/board/toradex/colibri-vf/readme.txt
> new file mode 100644
> index 0000000..a403c03
> --- /dev/null
> +++ b/board/toradex/colibri-vf/readme.txt
> @@ -0,0 +1,23 @@
Please add a short introduction paragraph here that indicates which HW
platforms are supported, if possible with links to the official website
for the platform.
> +Build instructions
> +------------------
> +
> +As a regular user configure and then build:
> +
> +$ make colibri_vf_defconfig
> +$ make
> +
> +This configuration will use a linux kernel and uboot from the git trees
> +maintained by Toradex and build a minimal root file system.
> +
> +Flashing the Vybrid module
> +--------------------------
> +
> +Details can be found at:
> +http://developer.toradex.com/knowledge-base/flashing-linux-on-vybrid-modules
> +
> +The above build configuration would result in building of rootfs.ubifs image
would result -> will result
> +and u-boot-nand.imx uboot binary. Prepare the SD card as per the instructions
> +on the above article. Replace the ubifs.img file in SD card with rootfs.ubifs
> +image file, rename it to ubifs.img and replace the u-boot-nand.imx uboot binary
> +on the SD card with the one generated by buildroot.
It is really not great that you have to prepare a complete SD card with
those weird instructions, and then replace some files with what
Buildroot has produced. What is so special about this SD card that
Buildroot cannot produce?
> Then follow the updation
updation -> update
> +procedure on the above article.
Could you fix the above issues, and send an updated version?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-31 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 7:06 [Buildroot] [PATCH v2 0/2] Add support for Toradex Colibri Vybrid modules Sanchayan Maity
2015-12-12 7:06 ` [Buildroot] [PATCH v2 1/2] configs: Add support for Toradex Colibri Vybrid Modules Sanchayan Maity
2016-05-31 21:19 ` Thomas Petazzoni
2016-06-03 11:22 ` maitysanchayan at gmail.com
2015-12-12 7:06 ` [Buildroot] [PATCH v2 2/2] board: Add a readme file for Toradex Colibri Vybrid module Sanchayan Maity
2016-05-31 21:23 ` Thomas Petazzoni [this message]
2016-06-03 11:25 ` maitysanchayan at gmail.com
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=20160531232342.556583b8@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox