Age | Commit message (Collapse) | Author |
|
If booting from SD card BCT contains information specific to SD card
partition layout which is bogus if used for NAND partition parsing.
Simply fall back to default offset just like in recovery BCT case.
Note: in the future we could parse SD partition table as well to more
generically support SD booting from various card densities.
|
|
Rather than relying on hard-coded offsets actually make use of
partition table parsing implementation.
|
|
NVIDIA's NAND layout includes a partition table that can be used to
generically construct the mtdparts kernel boot argument. As an added
benefit this is completely independent of the underlying NAND part
used which differs with various module versions. It further allows our
customer easy adoption to their own custom partition layout.
Initial partition table parsing courtesy of Mitja Špes from LXNAV.
|
|
Activate BL_ON backlight GPIO PT4 on SODIMM pin 71.
While at it add commented out XGA 1024x768 display timing values as well.
|
|
|
|
Link's MRC produces significantly more training data than
the one used on Stumpy/Lumpy.
Signed-off-by: Stefan Reinauer <reinauer@chromium.org>
BUG=none
TEST=boot tested on Link
Change-Id: I9310c3bcc77fb4318db0635b97b115ab0eb7e5ec
Reviewed-on: https://gerrit.chromium.org/gerrit/18748
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
|
|
BUG=none
TEST=check fmap on generated binary for unique names
Change-Id: Id1ac5cf223ec6a333fc8f4c587e972afd087f90d
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/18435
Reviewed-by: Stefan Reinauer <reinauer@google.com>
|
|
This saves 500ms in the RW BIOS path and still leaves 130K
overhead from the current U-boot size (372K) which should be
more than enough for any future updates on stumpy/lumpy.
This should be re-visited if/when vboot is smart enough to
just read+validate the actual binary within the section.
BUG=chrome-os-partner:8518
TEST=boot lumpy/stumpy through RW BIOS path and gather
timestamps to see 500ms improvement.
Change-Id: Ia714b4b95245f02f6e781247f820ca915bb403f5
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/18372
Reviewed-by: Stefan Reinauer <reinauer@google.com>
|
|
For some still unknown reason writes to localtion 0xcf9 do not cause
the Link to reboot, they cause it to shut down instead. While this
will have to be investigated and fixed, this change modifies the code
to use the keyboard controller (implemented by the EC on Link) to
restart the system.
Once the 0xcf9 problem is resolved, this change could be reverted.
BUG=chrome-os-partner:8397
TEST=manual
. when u-boot tires restarting the system it now reboots. before
this change it would just shut down.
Change-Id: I8076f897304f705e20ec8f2e30cce17d7fdd31c4
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/18332
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
|
|
BUG=chromium-os:23496
TEST=build on Waluigi, Seaboard, Cardhu
Change-Id: I9ccd3085fb551e9887815592e9b518b6944beda7
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/14474
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
BUG=chrome-os-partner:8180
TEST=Built u-boot for emeraldlake2.
Change-Id: Iae62f047ddc102fbf530e1f8f9af34939971a6a3
Signed-off-by: Gabe Black <gabeblack@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/18057
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Stefan Reinauer <reinauer@google.com>
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
|
|
This uses a format which is not supported by the upstream dtc, so
remove this.
BUG=chromium-os:23249
TEST=emerge-tegra2_kaen chromeos-u-boot with new dtc
Signed-off-by: Simon Glass <sjg@chromium.org>
Change-Id: I18b9420dbee20c2d115cc5ff1b13425faffe2a3e
Reviewed-on: https://gerrit.chromium.org/gerrit/17630
|
|
cold_reboot() should wait until the reset kicks in, instead of
returning and continuing in an undefined code path. Without this
patch, vboot_twostop will return, and secure_boot() will start
printing an error message, which results in a sporadic # on
the screen when pressing space or ESC on the dev screen in order
to go to recovery mode.
BUG=chrome-os-partner:7683
TEST=boot to dev screen on lumpy, press ESC or space. Observe
there is no # character printed before going to recovery
mode.
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Change-Id: Ic2ee570032686e48603f0fb3b1ec9cbfae9451bc
Reviewed-on: https://gerrit.chromium.org/gerrit/17007
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Commit-Ready: Stefan Reinauer <reinauer@chromium.org>
|
|
This will trigger setting gbb.flags to 1 in cros_bundle_firmware so the
factory time is reduced.
GBB.flags will be changed in the factory process.
Also needs https://gerrit.chromium.org/gerrit/#change,16845
BUG=chrome-os-partner:7671
TEST=manual
emerge-stumpy chromeos-bootimage
gbb_utility -g --flags /build/stumpy/firmware/image.bin
Should report "flags: 0x00000001"
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Change-Id: Ie05433ad737005bd5dcca2f88232b0a5bbd00df9
Reviewed-on: https://gerrit.chromium.org/gerrit/16113
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Commit-Ready: Stefan Reinauer <reinauer@chromium.org>
|
|
split the LP0 code for tegra2 into common
LP0 code and chip specific warm boot code
BUG=chromium-os:23496
TEST=build for Seaboard
Change-Id: Ie04bf9ac17482a37afd0f4515dc3aafeb4f48ae7
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/15883
|
|
This reverts commit 4c7502242627f64d91432cb4958be5f93f65fbff
Don't think this is the cause of http://code.google.com/p/chromium-os/issues/detail?id=26116, but it was in the same batch so I'm reverting in the process.
Change-Id: Icc013ced6c22e29d569ee4ca8ef73522154ec1a8
Reviewed-on: https://gerrit.chromium.org/gerrit/15561
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
|
|
split the LP0 code for tegra2 into common
LP0 code and chip specific warm boot code
BUG=chromium-os:23496
TEST=build for Seaboard
Change-Id: Id9756c08f61502affa8beee636d883d01468e6ec
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/13799
|
|
For Waluigi, existing frame buffer address does not fall
under external memory map.
Setting it to the location set as per the default initialization.
BUG=chromium-os:23496
TEST=Build ok for Cardhu, Waluigi and Seaboard. Tested on Waluigi.
Change-Id: I2284d43c11f4d6622344429508b1f99e30929f19
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/14698
|
|
Enables common LCD support for Tegra2 and Tegra3
BUG=chromium-os:23496
TEST=Built ok for Cardhu, Waluigi and Seaboard.
Change-Id: I938824045440cc4964c2ac6bf727a90ee5f129b4
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/14692
|
|
Add Waluigi keyboard map in Waluigi fdt
BUG=chromium-os:23496
TEST=Build and tested on Waluigi.
Change-Id: Iaf39dabc2bef2f12c2f0b875cc3c397386dbb446
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/13929
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
Add Keyboard controller option in tegra30 fdt.
BUG=chromium-os:23496
TEST=Build ok for Waluigi, Seaboard and Cardhu.
Change-Id: I20fe7feed42a96edea138dc32c532e0d1d535226
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/14546
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
Rename CONFIG_TEGRA2_KEYBOARD to common CONFIG_TEGRA_KEYBOARD
BUG=chromium-os:23496
TEST=Build OK for Waluigi, Cardhu and Seaboard.
Change-Id: Ice2741622fe6434ba25ece8fe7fbe2ca989c44ef
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/13930
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
Expand existing 4x6 keyboard support to 16x8 keyboard.
Add Tegra2 specific changes under Tegra2 config "CONFIG_TEGRA2".
BUG=chromium-os:23496
TEST=Tested on Waluigi.key press echoes the key on console.
Built ok for Cardhu and Seaboard.
Change-Id: Iab291a636d41b721d914014a5fe9ecc8775bf260
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/13928
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
BUG=none
TEST=manual
In dev-mode, press "Ctrl-U" with no USB stick inserted.
If "crossystem dev_boot_usb" is 0, you'll hear two 400Hz beeps.
If "crossystem dev_boot_usb" is 1, you'll hear one 200Hz beep.
Signed-off-by: Bill Richardson <wfrichar@google.com>
Change-Id: Ifd45a067ec8b922863331f13f3f4525ef40f7346
Reviewed-on: https://gerrit.chromium.org/gerrit/14529
Tested-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
Commit-Ready: Bill Richardson <wfrichar@chromium.org>
|
|
This is to match a change made in coreboot to align both
the header and the data to 16 bytes.
BUG=none
TEST=several cold boots to ensure that the MRC
data cache is not written out on every boot.
Change-Id: I6c9a01933264d6bd65958ddb93e8944c35e853c6
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/14096
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
|
|
dev_cfg is used by vboot_reference, hence we can't store our
u-boot environment there anymore. So create a section rw-environment
for that purpose.
Signed-off-by: Stefan Reinauer <reinauer@google.com>
BUG=chrome-os-partner:7264
TEST=boot tested on Stumpy
Change-Id: I15479f0f1a2aa111b742d2792052f48d660d122c
Reviewed-on: https://gerrit.chromium.org/gerrit/13022
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Commit-Ready: Stefan Reinauer <reinauer@chromium.org>
|
|
We need to make sure that the LCD is ready before we complete booting, so
put this code into board_late_init().
BUG=chromium-os:22938
TEST=build and boot on Kaen
Change-Id: I97bd1fce6ac93d0639dd8fdb17bf83e8a78d2645
Reviewed-on: https://gerrit.chromium.org/gerrit/13213
Commit-Ready: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
|
|
The LCD init takes place over five stages. We want to hide this init
behind other operations, so turn it into a state machine which we can
call at any time.
For now, call it in lcd_enable().
BUG=chromium-os:22938
TEST=build and boot on Kaen
Change-Id: Ia0b50ec74108ac4e015de12b7a9628426ea17656
Reviewed-on: https://gerrit.chromium.org/gerrit/13211
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
|
|
This will write magic value to APMC command port which
will trigger an SMI and cause coreboot to lock down
the ME, chipset, and CPU.
BUG=chrome-os-partner:6609
TEST=boot on stumpy+celeron and lumpy+i5 and ensure
the system still boots and that registers are locked
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Change-Id: Ib30ea83044f5123205531a5e8ee88ee37de2dd86
Reviewed-on: https://gerrit.chromium.org/gerrit/13604
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
|
|
- Depends on related Coreboot changes
- There is a 64k region allocated so use it all
- Write each data blob in a 4K aligned container
- Find the last entry in the region to compare against coreboot copy
- Detect a full region and erase it all and start over at zero
BUG=chrome-os-partner:6962
TEST=manual
I started writing an autotest for this, but it was taking more time
than just doing a thorough manual test. I will finish the autotest
but for now I relied on manual testing and using /sys/firmware/log
to tell what happened in Coreboot/U-boot on each boot.
TEST CASE 1 - newly flashed image:
1) Install the new bios with flashrom and reboot
2) Check that no MRC data was found by Coreboot in firmware log:
"prepare_mrc_cache: invalid MRC data"
3) Check that U-boot wrote training data in firmware log:
"handle_mrc_cache: cached storage mismatch (-1/2895)"
"firmware_storage_spi: before adjustment"
"firmware_storage_spi: offset: 0x1ec000"
"firmware_storage_spi: length: 0xb58"
"firmware_storage_spi: after adjustment"
"firmware_storage_spi: offset: 0x1ec000"
"firmware_storage_spi: length: 0x1000"
"firmware_storage_spi: offset: 0x001ec000"
"firmware_storage_spi: adjusted offset: 0x001ec000"
4) Check the flash to see if it has data in first slot
> flashrom -r /tmp/bios.now
> hexdump -Cv -s $((0x1ec000)) -n $((0x10000)) /tmp/bios.now
TEST CASE 2 - ensure that it uses the saved training data:
1) Reboot
2) Check that Coreboot used the training data in firmware log:
"prepare_mrc_cache: at ff9ec009, entry 0 size b4f checksum 9c"
3) Check that U-boot did not have to update the data in firmware log:
"handle_mrc_cache: cached storage match"
4) Check the flash to see if it still only has data in first slot:
> flashrom -r /tmp/bios.now
> hexdump -Cv -s $((0x1ec000)) -n $((0x10000)) /tmp/bios.now
TEST CASE 3 - ensure that it fills the next slot with new data:
1) Corrupt the seed checksum in CMOS:
> io_write8 0x70 0x78
> io_write8 0x71 0x00
2) Reboot
3) Check that Coreboot did not use cached data in firmware log:
"prepare_mrc_cache: invalid seed checksum"
4) Check that U-boot wrote new training data at new offset in firmware log:
"handle_mrc_cache: cached storage mismatch (2895/2895)"
"firmware_storage_spi: before adjustment"
"firmware_storage_spi: offset: 0x1ed000"
"firmware_storage_spi: length: 0xb58"
"firmware_storage_spi: after adjustment"
"firmware_storage_spi: offset: 0x1ed000"
"firmware_storage_spi: length: 0x1000"
"firmware_storage_spi: offset: 0x001ed000"
"firmware_storage_spi: adjusted offset: 0x001ed000"
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Change-Id: Ifffce29c5f9324f110c047a44a3f66d2e21cd6a4
Reviewed-on: https://gerrit.chromium.org/gerrit/13589
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Ronald G. Minnich <rminnich@chromium.org>
|
|
Coreboot was always using MTRR 7 for the write-protect
cache entry that covers the ROM and U-boot was removing it.
However with 4GB configs we need more MTRRs for the BIOS
and so the WP MTRR needs to move. Instead coreboot will
always use the last available MTRR that is normally set
aside for OS use and U-boot can clear it before the OS.
BUG=chrome-os-partner:7350
TEST=boot 4GB stumpy with coreboot MTRR fixes and verify
that U-boot does not clear MTRR 7 but does clear MTRR 9.
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Change-Id: Id6927325131b0b88043daa320a17847764626c0d
Reviewed-on: https://gerrit.chromium.org/gerrit/13477
Reviewed-by: Ronald G. Minnich <rminnich@chromium.org>
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
|
|
Add plumbing to support this option to delay console init until
after relocation.
BUG=chromium-os:22938
TEST=build and boot on Kaen
Change-Id: Iee3be9e2d0b51e6cf2f45a4408bfdde494c97d8b
Reviewed-on: https://gerrit.chromium.org/gerrit/13210
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
Commit-Ready: Simon Glass <sjg@chromium.org>
|
|
Move the serial init code into its own function to collect this all
in one place.
BUG=chromium-os:22938
TEST=build and boot on Kaen
Change-Id: I70162d836fddfabedd9cfbc07d8f0dc920602af8
Reviewed-on: https://gerrit.chromium.org/gerrit/13204
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Commit-Ready: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
|
|
We can support 8-bit eMMC and it is faster, so turn it on.
BUG=chromium-os:22938
TEST=build and boot on Kaen
Change-Id: I1509594832d317a086fa066d1a37c78a1a52c7c3
Reviewed-on: https://gerrit.chromium.org/gerrit/13201
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Commit-Ready: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
|
|
The Tegra2 can support this faster interface, so use it. It can reduce
data transfer time by about 40%.
BUG=chromium-os:22938
TEST=build and boot on Kaen
Change-Id: I656773c83083cd53d3ee52433e324e73fbcdc999
Reviewed-on: https://gerrit.chromium.org/gerrit/13200
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Reviewed-by: Tom Warren <twarren@nvidia.com>
Commit-Ready: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
This allows NAND to be disabled from the fdt easily.
BUG=chromium-os:22938
TEST=build and boot on Kaen
Signed-off-by: Fred
Signed-off-by: John
Change-Id: Ibf9259f8621e73fcf943f54a20327513288fef06
Reviewed-on: https://gerrit.chromium.org/gerrit/12913
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
Commit-Ready: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
|
|
Implement the VbExBeep function so that the DEV screen can beep.
Much of this code was coppied from coreboot.
BUG=chrome-os-partner:7114
TEST=manual, check that Stumpy beeps on DEV screen timeout and when
booting from USB with dev_boot_usb=0.
Change-Id: Icd4eabb0b10cc3d226db71e6a2b52d3ed7eb25ef
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/13110
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
|
|
BUG=chrome-os-partner:7185
TEST=emerge-* chromeos-u-boot chromeos-coreboot chromeos-bootimage
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Change-Id: I5361c9ba9519dd726adf9e91747fe08b5e79e9a7
Reviewed-on: https://gerrit.chromium.org/gerrit/13106
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
|
|
This patch moves the RW VPD section to the same place they live
at H2O and H2C for Stumpy and Lumpy, so we can preserve them more
easily when switching back and forth.
Also, add a RW shared section around the MRC cache and dev cfg,
so they get wiped by a recovery firmware update.
Signed-off-by: Stefan Reinauer <reinauer@google.com>
BUG=chrome-os-partner:7185
TEST=boot tested on Stumpy
Change-Id: I77778d17835b1fe4771370a3523b21c9e5a6b0a7
Reviewed-on: https://gerrit.chromium.org/gerrit/12990
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
|
|
BUG=chromium-os:23496
TEST=none
Modeled on tegra3-waluigi.dts
Signed-off-by: Tom Warren <twarren@nvidia.com>
Change-Id: I3a31084fa747991484dda4a40e89deda97a1ff1f
Reviewed-on: https://gerrit.chromium.org/gerrit/12939
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
H2C splits the flash device in 2 equal partitions of 4MB each.
In order to avoid having to adapt user space tools to coreboot,
change the flash map on Sandybridge to have the following flash
layout:
1.5MB SI_ (ME) sections
2.5MB RW sections
4.0MB RO sections
BUG=none
TEST=boot tested on Stumpy
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Change-Id: Ida0864389644b07b2d284770be62447547fdfb2e
Reviewed-on: https://gerrit.chromium.org/gerrit/12937
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Tested-by: Stefan Reinauer <reinauer@chromium.org>
|
|
BUG=chromium-os:23496
TEST=built Seaboard and Waluigi OK
Signed-off-by: Tom Warren <twarren@nvidia.com>
Change-Id: I00f6cde99ec4473da3d571fffb1e4adde7828822
Reviewed-on: https://gerrit.chromium.org/gerrit/12443
|
|
BUG=chromium-os:23496
TEST=built Seaboard and Waluigi OK
Signed-off-by: Tom Warren <twarren@nvidia.com>
Change-Id: I40147ab6d07cc13ef255736f0ebdabe34f85addf
Reviewed-on: https://gerrit.chromium.org/gerrit/12441
Commit-Ready: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
BUG=chromium-os:23496
TEST=built Seaboard and Waluigi OK
Signed-off-by: Tom Warren <twarren@nvidia.com>
Change-Id: I918a326749272032a682dea7c27d86494da31a6f
Reviewed-on: https://gerrit.chromium.org/gerrit/12440
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Commit-Ready: Simon Glass <sjg@chromium.org>
|
|
- obsolete alex fmap is not updated.
- drop unused shared-section, ro-recovery, ro-data
- make coreboot CBFS 1MB
- make GBB 512KB
- align RW-A and RW-B to 1MB
- increase rw-mrc-cache to 64KB for RW level wearing
BUG=chrome-os-partner:7172
TEST=boot coreboot on Stumpy and see it still booting
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Change-Id: I4da3b6bf1023bacadaa9b2e07eb07500247e120c
Reviewed-on: https://gerrit.chromium.org/gerrit/12704
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
|
|
- SI_ME size is now 1.5MB (down from 2MB)
- SI_BIOS size is now 6.5MB (up from 6MB)
- coreboot-extra region increases by 512K to consume the new space
BUG=chrome-os-partner:7147
TEST=boot on stumpy and lumpy with updated descriptor and ME
Change-Id: I77e720e453901f9dcfe861e4c41447bf9832f919
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/12654
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
|
|
detect keypress at startup on the USB keyboard since we have no internal
keyboard.
BUG=chrome-os-partner:5752
TEST=on Stumpy, check Ctrl+U, Ctrl+D and space are working as
expected in dev mode.
Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
Change-Id: I34762f528817ffd29fa5a1198473f030887990bd
Reviewed-on: https://gerrit.chromium.org/gerrit/12583
Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
|
|
If the primary input of the device is a USB keyboard (as defined by the
FDT) and we are in developer mode, enumerate the USB devices at startup
and get key strokes from USB keyboard.
The keyboard reading is not working correctly yet on the recovery path
due to the USB mass storage polling code doing continuous re-enumeration
on the USB controller.
BUG=chrome-os-partner:5752
TEST=tested on Stumpy and Lumpy, with and without usb-keyboard set in the
device tree, check Ctrl+U, Ctrl+D and space are working as expected.
Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
Change-Id: Ib46d6086ae5e5ce631d5f91b467f7b2bf90644d0
Reviewed-on: https://gerrit.chromium.org/gerrit/12543
Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
The flash map needs to be reshuffled because the Ivy Bridge MRC does
not fit into the room Sandy bridge MRC used to fit in (512K are
required instead of 256K), so the entire boot stub gets now 1M instead
of 512K.
link.dts is also being modified as appropriate.
BUG=chrome-os-partner:6707
TEST=none
Change-Id: I2cb6ef9319d57233f5254063d7c35f135fd34a52
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/12605
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
|
|
This is a copy of the Sandy Bridge flash map and the device tree with
no modifications. Ivy Bridge requires more room for the MRC, and as
such it requires its own flash map, the SB map and the dts wrapper
will be used as the prototypes.
BUG=chrome-os-partner:6707
TEST=none
Change-Id: I25b5f7006f98991724da7b28ab6170a333495400
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/12604
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Gabe Black (Do Not Use) <gabeblack@google.com>
|