Automate bitmap image regeneration.

Automate bitmap image regeneration.

This CL modifies the bitmap generation script as follows:

- allow to specify required geometry of the images and to
 generate a single set per FWID instead of generating all
 geometries for all FWIDs

- store the images and the zip archive in a directory with
  the name derived from FWID.

The CL also adds a wrapper, which given the path to the tree
containing already released GBB firmware volumes would find
all valid (as verified by the CRC in the file name) FWIDs
and generate new images for all detected FWIDs.

The geometry of the generated images is based on the FWID
contents, Marios get 1280x800 and ZGAs - 1366x768.

Once this script stops running, the scripts/bitmaps
directory contains a set of subdirectories, one per
generated set of images.

Another script ran by cygwin on a windows machine was used
to pick up all image sets and regenerate GBB firmware
volumes, will be published under a separate CL.


BUG=chrome-os-partner:792
TEST=see below:

Ran the following command:
 ./process_all_targets.sh  ../../../chromeos-internal/third_party/autotest/files/client/site_tests/

After command completed, the following out_* directories showed up:

(bitmaps 144) ls -1d out*
out_ACER_ASPIREONE_001_8012/
out_ACER_ASPIREONE_001_DEV_0393/
out_ACER_ASPIREONE_002_0710/
out_ACER_ASPIREONE_002_DEV_1017/
out_IEC_MARIO_FISH_2330/
out_IEC_MARIO_PONY_6101/
out_IEC_MARIO_PONY_DEV_3342/
out_IEC_MARIO_PONY_DVT_8784/
out_IEC_MARIO_PONY_EVT_3495/
out_IEC_MARIO_PONY_PREDVT_6766/

with typical directory contents as follows:

(bitmaps 145) tree out_ACER_ASPIREONE_001_8012/
out_ACER_ASPIREONE_001_8012/
|-- 1366x768.zip
|-- BlankBmp
|   `-- BlankBmp.bmp
|-- DeveloperBmp
|   `-- DeveloperBmp.bmp
|-- RecoveryBmp
|   `-- RecoveryBmp.bmp
|-- RecoveryMissingOSBmp
|   `-- RecoveryMissingOSBmp.bmp
`-- RecoveryNoOSBmp
    `-- RecoveryNoOSBmp.bmp

5 directories, 6 files

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=10fce4a

[vb, 2010-10-28 00:44:30]

Bill, what's the bug number for this issue - I did not see anything appropriate
on either tracker.

[Bill Richardson, 2010-10-28 15:28:53]

LGTM.

This is much nicer. Thanks, Vadim!

http://codereview.chromium.org/4147008/diff/2001/3002
File scripts/bitmaps/process_all_targets.sh (right):

http://codereview.chromium.org/4147008/diff/2001/3002#newcode29
scripts/bitmaps/process_all_targets.sh:29: # string's CRC32 and print the last
for hex digits of the crc.
s/for/four/

[Bill Richardson, 2010-10-28 17:09:29]

Oh, and the bug is
http://code.google.com/p/chrome-os-partner/issues/detail?id=792

[Randall Spangler, 2010-10-28 17:20:09]

LGTM

[vb, 2010-10-29 15:08:03]

http://codereview.chromium.org/4147008/diff/2001/3002
File scripts/bitmaps/process_all_targets.sh (right):

http://codereview.chromium.org/4147008/diff/2001/3002#newcode29
scripts/bitmaps/process_all_targets.sh:29: # string's CRC32 and print the last
for hex digits of the crc.
On 2010/10/28 15:28:54, Bill Richardson wrote:
> s/for/four/

Done.