From: Tom Rini <trini@ti.com>
To: "Maxin B. John" <maxin.john@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] u-boot-fw-utils: install config file
Date: Thu, 26 Jun 2014 09:47:20 -0400 [thread overview]
Message-ID: <20140626134720.GO9006@bill-the-cat> (raw)
In-Reply-To: <20140626133407.GA20735@sestofb10.enea.se>
On Thu, Jun 26, 2014 at 03:34:07PM +0200, Maxin B. John wrote:
> Hi Tom,
>
> On Thu, Jun 26, 2014 at 08:27:00AM -0400, Tom Rini wrote:
> > On Wed, Jun 25, 2014 at 11:13:59AM +0200, Maxin B. John wrote:
> > > From: "Maxin B. John" <maxin.john@enea.com>
> > >
> <snip>
> > > + install -m 0644 ${S}/tools/env/fw_env.config ${D}${sysconfdir}/fw_env.config
> > > }
> > >
> > > PACKAGE_ARCH = "${MACHINE_ARCH}"
> >
> > We should really provide some way for the BSP to provide a functional
> > fw_env.config file as the one in the sources is mainly an example and
> > unlikely to work on most systems.
> I do agree that it is just an example file. However, without the configuration
> file, fw_printenv will fail with this warning:
>
> #fw_printenv
> Cannot parse config file: No such file or directory
>
> IMHO, those who want to use a "real" config file, should use a proper ".bbappend"
> eg:
>
> do_install_append() {
>
> case "${MACHINE}" in "mymachine" )
> echo ' myargs '> ${D}${sysconfdir}/fw_env.config;;
> *);;
>
> esac
> }
>
> Is this an acceptable way or should we modify it ?
Ah, OK, cobwebs dusted off. The u-boot recipe currently provides
fw_env.config correct for the board in question, so long as it's
provided.
--
Tom
prev parent reply other threads:[~2014-06-26 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 9:13 [PATCH] u-boot-fw-utils: install config file Maxin B. John
2014-06-26 12:27 ` Tom Rini
2014-06-26 13:34 ` Maxin B. John
2014-06-26 13:47 ` Tom Rini [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=20140626134720.GO9006@bill-the-cat \
--to=trini@ti.com \
--cc=maxin.john@enea.com \
--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