Board:google/butterfly: Difference between revisions
| Line 6: | Line 6: | ||
=== Including the MAC address and keyboard layout === | === Including the MAC address and keyboard layout === | ||
NOTE: The patches to make this work have not been merge yet. This information is strictly PRELIMINARY!!!. | |||
The coreboot that ships with the laptop will read the keyboard layout and MAC address from the flash. Since ChromeOS uses a different layout than CBFS, the region containing these parameters must me included in the CBFS of the custom coreboot. There is [http://review.coreboot.org/4307 a patch] to allow coreboot to read this file and configure the hardware accordingly. | The coreboot that ships with the laptop will read the keyboard layout and MAC address from the flash. Since ChromeOS uses a different layout than CBFS, the region containing these parameters must me included in the CBFS of the custom coreboot. There is [http://review.coreboot.org/4307 a patch] to allow coreboot to read this file and configure the hardware accordingly. | ||
Revision as of 20:09, 3 December 2013
See Chromebooks for additional details.
Hi. I am the mighty alien dwarf, and I will be talking about the Pavilion Chromebook here.
Building a complete coreboot image (WHIP)
Including the MAC address and keyboard layout
NOTE: The patches to make this work have not been merge yet. This information is strictly PRELIMINARY!!!.
The coreboot that ships with the laptop will read the keyboard layout and MAC address from the flash. Since ChromeOS uses a different layout than CBFS, the region containing these parameters must me included in the CBFS of the custom coreboot. There is a patch to allow coreboot to read this file and configure the hardware accordingly.
Get 'flashmap'
$ git clone https://chromium.googlesource.com/chromiumos/third_party/flashmap
Find the RO_VPD section
Build flashmap, then run fmap_decode on the extracted chromebook firmware.
$ ./fmap_decode original_chrome_image.rom
Locate the RO_VPD section in the output:
area_offset="0x00600000" area_size="0x00004000" area_name="RO_VPD" area_flags_raw="0x01" area_flags="static"
Extract the RO_VPD section from ROM image.
First, convert area_offset and area_size to decimal, as dd does not accept hexadecimal input, then use dd to extract the RO_VPD section.
$ dd if=original_chrome_image.rom bs=1 skip=ibs=$((area_offset)) count=$((area_size)) of=vpd.bin
Insert vpd.bin in the custom coreboot image:
$ cbfstool build/coreboot.rom add -f vpd.bin -n vpd.bin -t raw