the following patch was just integrated into master:
commit 4e92f69015c849b719b76884d64eb12bccc07bcd
Author: Aaron Durbin <adurbin(a)chromium.org>
Date: Thu Oct 10 21:03:50 2013 -0500
baytrail: add vboot ramstage verification
Add suport for verifying the ramstage with vboot
during romstage execution. Along with this support
select CACHE_RELOCATED_RAMSTAGE_OUTSIDE_CBMEM to
cache the relocated ramstage 1MiB below the
top end of the TSEG region.
BUG=chrome-os-partner:23249
BRANCH=None
TEST=Built and booted with CONFIG_VBOOT_VERIFY_FIRMWARE=y
selected.
Signed-off-by: Aaron Durbin <adurbin(a)chromium.org>
Change-Id: I355f62469bdcca62b0a4468100effab0342dc8fc
Reviewed-on: https://chromium-review.googlesource.com/172712
Reviewed-by: Shawn Nematbakhsh <shawnn(a)chromium.org>
See http://review.coreboot.org/4880 for details.
-gerrit
the following patch was just integrated into master:
commit 714c10d58294ff8f628b62c959f2ad8d86f7eee7
Author: Oskar Enoksson <enok(a)lysator.liu.se>
Date: Tue Feb 11 23:19:02 2014 +0100
Eliminate some ASL warnings
The ASL compiler warned about "Control Method should be made Serialized
(due to creation of named objects within)". This commit eliminates the
warnings by changing those NonSerialized into Serialized.
Change-Id: I639e769cf7a9428c34268e0c555a30c7dee1e04c
Signed-off-by: Oskar Enoksson <enok(a)lysator.liu.se>
See http://review.coreboot.org/5189 for details.
-gerrit
the following patch was just integrated into master:
commit ac5ffb75785135386c1b4dc52d4f6d0bdf151f49
Author: Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
Date: Wed Feb 12 15:54:47 2014 -0600
google boards: Do not hardcode location of spd.bin
spd.bin can reside anywhere in CBFS, and we only use CBFS APIs to
access and read it. As such, there is no need to hardcode it, and it
can collide with mrc.bin or mrc.cache on some boards. Do not use a
specific position for spd.bin, but instead let cbfstool find the
optimal placement.
Change-Id: I496094d3c0de708813494095b7ac4be8addb4112
Signed-off-by: Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
See http://review.coreboot.org/5210 for details.
-gerrit
the following patch was just integrated into master:
commit 1bba4c1b1495ab44d1331bffedfe1c11357ce67f
Author: Shawn Nematbakhsh <shawnn(a)chromium.org>
Date: Fri Oct 11 12:39:48 2013 -0700
baytrail: gpio: add configs for PU/PD functional pins
Pull-ups and pull-downs can be active on functional pins. Add configs
for these options so they can be specified on board GPIO maps.
TEST=Manual on bayleybay. Verify that platform boots to payload load.
BUG=chrome-os-partner:22863
Change-Id: Ie4f77d8ce812f086cc8fe5a6bfcac59669f56f92
Signed-off-by: Shawn Nematbakhsh <shawnn(a)chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/172766
Signed-off-by: Aaron Durbin <adurbin(a)chromium.org>
See http://review.coreboot.org/5209 for details.
-gerrit
the following patch was just integrated into master:
commit 5a9c0814ff5d2064e17f4696ac05ab6dce8404aa
Author: Duncan Laurie <dlaurie(a)chromium.org>
Date: Tue Feb 11 10:43:21 2014 -0800
falco: Add ACPI code to describe the I2C touchpad device
If the SerialIO devices are put into ACPI mode then it is possible
to use ACPI to instantiate the touchpad in the kernel without
needing to have a platform level driver to do the binding.
This is the "new way" of describing on-board I2C devices and the
upstream kernel is starting to add ACPI IDs to drivers so they can
be used in this fashion. For the Cypress touchpad use a generic
ACPI ID of "CYPA0000" to describe it.
In order to support the proper scoping of the touchpad device under
the appropriate I2C controller device the mainboard.asl file needs
to be included after pch.asl so the I2C device exists.
Change-Id: I81e053d27be478f3a19b6f9b13cd2b4fabcb88c0
Signed-off-by: Duncan Laurie <dlaurie(a)chromium.org>
See http://review.coreboot.org/5194 for details.
-gerrit