
12 Aug
2010
12 Aug
'10
4:42 p.m.
On Wed, Aug 11, 2010 at 11:42 PM, Mike Frysinger vapier@gentoo.org 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
Applies clean to 69a2a4d9a5884a6f2d04a551308980d452b9b349 of git://git.denx.de/u-boot.git.
Tested on da850evm_config with NAND enabled, board boots fine.
Tested-by: Ben Gardinerbengardiner@nanometrics.ca
--- Nanometrics Inc. http://www.nanometrics.ca