24 Apr
2009
24 Apr
'09
11:47 p.m.
On 10:21 Fri 24 Apr , Scott Wood wrote:
On Fri, Apr 24, 2009 at 02:57:52PM +0900, Kyungmin Park wrote:
Actually, I don't like the CONFIG_SYS_MONITOR_LEN approaches, now you are consider the bad block at 1. But we can also consider the bad block 2, if there two consecutive 2 bad block at block 1, 2, we should define the CONFIG_SYS_MONITOR_LEN as 128KiB * 4 and reserved block block 4 always even though we use 2 blocks.
There are two separate constants -- the length of data excluding bad blocks, and the size of the region set aside for that data including bad blocks. CONFIG_SYS_MONITOR_LEN is the former.
we may need to detect the u-boot.bin size dynamicly instead of staticly
as Scott NACK
Best Regards, J.