Add the nand device support for cbootimage tool.

Add the nand device support for cbootimage tool.

Change-Id: Ic24dd4c971c16d00742d90830be168b41483be7a

BUG=None.
TEST=Test with the config file.

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=053d578

[robotboy, 2011-03-03 18:08:46]

LGTM, with a couple of questions below.  I'll push it as is because it passes my
tests, but it would be good to know if the changes are related to a bug I'm
tracking.

Thanks,
    Anton

http://codereview.chromium.org/6611009/diff/1/cbootimage.c
File cbootimage.c (right):

http://codereview.chromium.org/6611009/diff/1/cbootimage.c#newcode180
cbootimage.c:180: begin_update(&context);
Is this required for the NAND support or is it a separate bug fix?

http://codereview.chromium.org/6611009/diff/1/data_layout.c
File data_layout.c (right):

http://codereview.chromium.org/6611009/diff/1/data_layout.c#newcode898
data_layout.c:898: SET_VALUE(boot_data_version, NVBOOT_BOOTDATA_VERSION(2, 1));
Similarly here, is this just a bug fix?

[robotboy, 2011-03-03 18:09:30]

On 2011/03/03 18:08:46, robotboy wrote:
> LGTM, with a couple of questions below.  I'll push it as is because it passes
my
> tests, but it would be good to know if the changes are related to a bug I'm
> tracking.
> 
> Thanks,
>     Anton
> 

FYI, the bug I'm working on that might be related is:
http://code.google.com/p/chromium-os/issues/detail?id=12712

Thanks,
    Anton

[pchen, 2011-03-04 02:18:04]

On 2011/03/03 18:09:30, robotboy wrote:

The previous cbootimage was designed only use for edit the existing .bct file
then append the bootloader and google component.
I add the code you point out above to correctly generate the .bct file just base
on the description in config file, in that case no existing .bct for reference.

I'm not quite understand you description in issue-12712, do you mean if the
cbootimage modify the boot device field of .bct file, the generated image will
not boot?