Dear Vitaly Bordug,
repl: bad addresses:
linuxppc-...@ozlabs.org linuxppc-...@ozlabs.org -- junk after
lo...@domain ()
In message 20091216024730.455b9...@vitb-lp you wrote:
From: Heiko Schocher h...@denx.de
This driver provides (read/write) access to the
U-Boot bootcounter via
On Wed, Dec 16, 2009 at 02:47:30AM +0300, Vitaly Bordug wrote:
From: Heiko Schocher h...@denx.de
This driver provides (read/write) access to the
U-Boot bootcounter via PROC FS or sysFS.
in u-boot, it uses a 8 byte mem area (it must hold the value over a
soft reset of course), for
[...]
bootco...@0x3eb0 {
device_type = bootcount;
Clear.
No device_type.
compatible = uboot,bootcount;
reg = 0x3eb0 0x08;
};
This area should also be in the flattened tree's reserved map.
Can you elaborate
В Thu, 17 Dec 2009 10:34:34 +0100
Wolfram Sang w.s...@pengutronix.de пишет:
On Wed, Dec 16, 2009 at 02:47:30AM +0300, Vitaly Bordug wrote:
From: Heiko Schocher h...@denx.de
This driver provides (read/write) access to the
U-Boot bootcounter via PROC FS or sysFS.
in u-boot, it
В Thu, 17 Dec 2009 09:16:07 +0100
Wolfgang Denk w...@denx.de пишет:
Dear Vitaly Bordug,
repl: bad addresses:
linuxppc-...@ozlabs.org linuxppc-...@ozlabs.org -- junk
after lo...@domain () In message 20091216024730.455b9...@vitb-lp
you wrote:
From: Heiko Schocher h...@denx.de
From: Heiko Schocher h...@denx.de
This driver provides (read/write) access to the
U-Boot bootcounter via PROC FS or sysFS.
in u-boot, it uses a 8 byte mem area (it must hold the value over a
soft reset of course), for storing a bootcounter (it counts many soft
resets are done, on hard reset it
On Wed, Dec 16, 2009 at 02:47:30AM +0300, Vitaly Bordug wrote:
From: Heiko Schocher h...@denx.de
This driver provides (read/write) access to the
U-Boot bootcounter via PROC FS or sysFS.
in u-boot, it uses a 8 byte mem area (it must hold the value over a
soft reset of course), for
