From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] u-boot-fw-utils: Initial version
Date: Sat, 04 Feb 2012 00:06:40 +0100 [thread overview]
Message-ID: <1328310400.4220.60.camel@mattotaupa> (raw)
In-Reply-To: <1328309610-12397-1-git-send-email-tom.rini@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
Dear Tom,
Am Freitag, den 03.02.2012, 15:53 -0700 schrieb Tom Rini:
> From: Tom Rini <trini@ti.com>
please add the version in the commit summary.
> This provides the 'fw_setenv' and 'fw_getenv' programs for the target
> so that the U-Boot environment can be modified from Linux. These
> programs are system-agnostic and rely on a config file that a given BSP
> will provide (and RRECOMMEND this be installed).
I do not understand the addition in the parentheses.
> Signed-off-by: Tom Rini <trini@ti.com>
> ---
> meta/recipes-bsp/u-boot/u-boot-fw-utils_2011.06.bb | 26 ++++++++++++++++++++
> 1 files changed, 26 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-bsp/u-boot/u-boot-fw-utils_2011.06.bb
>
> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2011.06.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2011.06.bb
> new file mode 100644
> index 0000000..3185cbd
> --- /dev/null
> +++ b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2011.06.bb
> @@ -0,0 +1,26 @@
> +DESCRIPTION = "U-boot bootloader fw_printenv/setenv utils"
> +LICENSE = "GPLv2+"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb \
> + file://README;beginline=1;endline=22;md5=5ba4218ac89af7846802d0348df3fb90"
> +SECTION = "bootloader"
Is this the standard ordering? Is there also a homepage for theses
utils?
> +
> +PR = "r0"
> +
Was a decision made if `PR = "r0"` should be set?
> +SRC_URI = "ftp://ftp.denx.de/pub/u-boot/u-boot-${PV}.tar.bz2"
> +
> +SRC_URI[md5sum] = "0cc5026aad02f218a9b9ac56b301c97a"
> +SRC_URI[sha256sum] = "362ddb935885da98cf461eba08f31e3e59d0c4ada6cb2fa15596f43af310ba8b"
> +
> +S = "${WORKDIR}/u-boot-${PV}"
Is that the default? I always forget.
> +
> +EXTRA_OEMAKE = 'HOSTCC="${CC}"'
> +
> +do_compile () {
> + oe_runmake env
> +}
> +
> +do_install () {
> + install -d ${D}${base_sbindir}
> + install -m 755 ${S}/tools/env/fw_printenv ${D}${base_sbindir}/fw_printenv
> + install -m 755 ${S}/tools/env/fw_printenv ${D}${base_sbindir}/fw_setenv
> +}
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-02-03 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:53 [PATCH] u-boot-fw-utils: Initial version Tom Rini
2012-02-03 23:06 ` Paul Menzel [this message]
2012-02-04 0:34 ` Koen Kooi
2012-02-08 17:57 ` Tom Rini
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=1328310400.4220.60.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=openembedded-core@lists.openembedded.org \
/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