
13 Aug
2010
13 Aug
'10
8:33 p.m.
On Wed, Aug 11, 2010 at 11:42:26PM -0400, Mike Frysinger wrote:
Currently, if there is an error probing the NAND chip and the env is based in NAND, the readenv() function will use a NULL function pointer and thus jump to address 0.
Here I just check for a non-zero value of blocksize as that shouldn't be zero when a valid device is found, but perhaps there is a better way for someone familiar with the NAND internals to suggest.
Signed-off-by: Mike Frysinger vapier@gentoo.org
common/env_nand.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
Applied to u-boot-nand-flash.
-Scott