From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Çağlar Kilimci" <ckilimci@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: Reach out "dirty" state value
Date: Tue, 25 Apr 2017 07:51:30 +0200 [thread overview]
Message-ID: <20170425055130.x7zhlezvpkb7hmx3@pengutronix.de> (raw)
In-Reply-To: <CAGUZs0k15t=zEVwjsjUAxvRaow2c-UTm+0NKbkiYCXO_kAhPew@mail.gmail.com>
Hi Çağlar,
On Mon, Apr 24, 2017 at 11:20:47AM +0300, Çağlar Kilimci wrote:
> Hi all,
>
> I would like to use state framework and now I can read variables from
> both barebox and regular kernel space. In addition, if I can change
> from barebox, I can successfully read the changes from kernel space
> but if I change from kernel space, I could not reach out the new value
> from barebox. The dirty variable is set and I can see the new value
> from eeprom (where I store the values) but I guess there would be
> better way to reach out the "dirty" values. So, how can I read last
> value for that state variable?
If you get outdated variables in barebox that's a bug. You are on latest
master, right? Do you have stridesize specified in the devicetree?
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-04-25 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 8:20 Çağlar Kilimci
2017-04-25 5:51 ` Sascha Hauer [this message]
2017-04-25 6:08 ` Çağlar Kilimci
2017-04-25 6:42 ` Sascha Hauer
2017-04-25 9:17 ` Çağlar Kilimci
2017-04-25 13:08 ` Çağlar Kilimci
2017-04-25 13:24 ` Çağlar Kilimci
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=20170425055130.x7zhlezvpkb7hmx3@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