From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe BEGUE <begue.jc@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Programatically write in a file in the environnent with a hush command
Date: Wed, 27 May 2015 08:53:00 +0200 [thread overview]
Message-ID: <20150527065300.GP6325@pengutronix.de> (raw)
In-Reply-To: <CABP==CLFeG59X3OyMxJrxTzWDg-Xm8dURb-k-JXu3as+pY5mKA@mail.gmail.com>
Hi Jean-Christophe,
On Tue, May 26, 2015 at 05:41:06PM +0200, Jean-Christophe BEGUE wrote:
> Hello,
>
> I'm trying to pass a value from Barebox to the operating system, using
> the usreland command bareboxenv -l.
>
> My problem is : How should I write that status from my hush barebox script?
>
> echo $mystatus > /env/data/my_status_file
>
> The above command doesn't work as '>' is not implemented.
>
> I've the feeling that I'm missing something?
Besides the ways Alexander just mentioned you could also add something
to the kernel cmdline and parse /proc/cmdline later in userspace.
Still another possibility is to add nodes/properties to the device tree
using the of_* commands.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-05-27 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 15:41 Jean-Christophe BEGUE
2015-05-27 6:08 ` Alexander Richter
2015-05-27 6:24 ` Alexander Richter
2015-05-27 6:53 ` Sascha Hauer [this message]
2015-05-27 13:52 ` Jean-Christophe BEGUE
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=20150527065300.GP6325@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=begue.jc@gmail.com \
/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