From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Çağlar Kilimci" <ckilimci@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: State Framework and dtb
Date: Thu, 30 Mar 2017 08:31:39 +0200 [thread overview]
Message-ID: <20170330063139.kfxjxb33cbrbzrdp@pengutronix.de> (raw)
In-Reply-To: <CAGUZs0n9Piigr3=NTt4vz2YhMz_TKzhUtfKewRrGzk=dNT0=Dw@mail.gmail.com>
On Wed, Mar 29, 2017 at 04:24:11PM +0300, Çağlar Kilimci wrote:
> Hi all,
>
> Previously, I ask for a help [1] and thankfully Sascha replied with
> helpful comments then I have tried many dts configurations but I still
> could not run state framework.
>
> My main goal is to update a system using RAUC [2] so I need state
> framework of barebox. I would like to use EEPROM as a storage device
> for barebox state. Here is an example dts that I think, it should have
> work:
> state: state@0 {
> magic = <0x27031977>;
> compatible = "barebox,state";
> backend-type = "dtb";
> backend = &state_partition;
This should be a phandle. Sorry, the example I gave you last time was
wrong. It should be
backend = <&state_partition>;
Note the '<>'
> barebox@Phytec phyCORE AM335x:/ oftree -p
I'm not sure this works as expected. You should rather modify the
devicetree in the barebox binary.
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:[~2017-03-30 6:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 13:24 Çağlar Kilimci
2017-03-30 6:31 ` Sascha Hauer [this message]
2017-03-30 10:33 ` Çağlar Kilimci
2017-03-31 6:21 ` Sascha Hauer
2017-03-31 6:54 ` Çağlar Kilimci
2017-03-31 7:02 ` Sascha Hauer
2017-03-31 7:18 ` Çağlar Kilimci
2017-03-31 7:23 ` Sascha Hauer
2017-03-31 11:41 ` Çağlar Kilimci
2017-03-31 13:00 ` Sascha Hauer
2017-04-03 20:59 ` Çağlar Kilimci
2017-04-04 6:22 ` Sascha Hauer
2017-04-04 6:49 ` Çağlar Kilimci
2017-04-04 8:04 ` Jan Remmet
[not found] ` <58e3539f.0582540a.1e64d.751fSMTPIN_ADDED_BROKEN@mx.google.com>
2017-04-04 10:27 ` Çağlar Kilimci
2017-04-04 10:48 ` Ian Abbott
2017-04-05 6:01 ` Sascha Hauer
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=20170330063139.kfxjxb33cbrbzrdp@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ckilimci@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