Re: Reach out "dirty" state value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox




[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux