mail archive of the barebox mailing list
 help / color / mirror / Atom feed
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: Fri, 31 Mar 2017 08:21:40 +0200	[thread overview]
Message-ID: <20170331062139.d5kaoagglgnylr2r@pengutronix.de> (raw)
In-Reply-To: <CAGUZs0n93ZWNASvyyUddCPfSKPYavomXxGwHMd6caGGn3w65hw@mail.gmail.com>

On Thu, Mar 30, 2017 at 01:33:26PM +0300, Çağlar Kilimci wrote:
> Hi,
> 
> >>   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 '<>'
> It's alright. I applied the changes, but still no registered state
> instances there. Similarly, if I free stored device tree and load it
> back again; before probe it, I can observe state like this:

I should have never implemented this freeing of the stored device tree.
There are too many pointers in the code to nodes of this tree. Please
do not use this free/load device tree feature for state. So you edited
the devicetree in the barebox source code, built a new binary with it
and started it. Now when you enter "of_dump /state@0" you should
see the state node you created. Is that what happens?

> 
> I appended many configs even if I do not need all of them:

The configs seem to have everything necessary

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

  reply	other threads:[~2017-03-31  6:22 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
2017-03-30 10:33   ` Çağlar Kilimci
2017-03-31  6:21     ` Sascha Hauer [this message]
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=20170331062139.d5kaoagglgnylr2r@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