| <?xml version="1.0" encoding="utf-8"?><manifest revision="71721b498ab5d6be71a358fbc81fd0a570f39289"> |
| <notice>Your sources have been sync'd successfully.</notice> |
| <remote fetch="https://android.googlesource.com" name="aosp" review="https://android-review.googlesource.com"/> |
| <remote alias="cros" fetch="https://chromium.googlesource.com/" name="chromium"/> |
| <remote fetch="https://chromium.googlesource.com" name="cros" review="https://chromium-review.googlesource.com"/> |
| <default remote="cros" revision="refs/heads/master" sync-j="8"/> |
| <project name="aosp/platform/external/libchrome" path="src/aosp/external/libchrome" revision="5ca6b5581735fdb7a46249d4eb587aff936434f5" upstream="refs/heads/master"/> |
| <project name="aosp/platform/external/modp_b64" path="src/third_party/modp_b64" revision="afc3e28a3de4a627e3afaf73b4c55ed85c992470" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/core/libsync" path="src/aosp/system/libsync" revision="f4f4387b6bf2387efbcfd1453af4892e8982faf6" upstream="refs/heads/master"/> |
| <project groups="devserver" name="aosp/platform/system/update_engine" path="src/aosp/system/update_engine" revision="21ac9965fbd4a3dc5401f9b529224b9728fac469" upstream="refs/heads/master"/> |
| <project name="apps/libapps" path="src/third_party/libapps" revision="ee73d416ac61fd2d51400557b32aef362012918a" upstream="refs/heads/master"> |
| <annotation name="branch-mode" value="pin"/> |
| </project> |
| <project name="chromium/deps/libmtp" path="chromium/src/third_party/libmtp" remote="chromium" revision="4f4fad584e9c2735af5131f15b697376a3327de5" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools,labtools" name="chromium/llvm-project/cfe/tools/clang-format" path="src/chromium/src/buildtools/clang_format/script" remote="chromium" revision="2b978b6c40e8f0c6829427559f4e629a4b2608a2" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools,labtools" name="chromium/src/buildtools" path="src/chromium/src/buildtools" remote="chromium" revision="09893e534d6df18471314f47af5c3f51336e8827" upstream="refs/heads/master"/> |
| <project name="chromium/src/third_party/Python-Markdown" path="src/chromium/src/third_party/Python-Markdown" remote="chromium" revision="b08af21eb795e522e1b972cb85bff59edb1ae209" upstream="refs/heads/master"/> |
| <project name="chromium/src/tools/md_browser" path="src/chromium/src/tools/md_browser" remote="chromium" revision="2a89b085abac9d04563abc47833e2bf85383620c" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,labtools" name="chromium/tools/depot_tools" remote="chromium" revision="7639f1999ac1d8992fc4fbb169d164b156d9a7f7"/> |
| <project groups="minilayout,firmware,buildtools,chromeos-admin,labtools,sysmon,devserver" name="chromiumos/chromite" path="chromite" revision="17937cb2333ca78145b02b48cba9d02ba78de06c" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/containers/cros-container-guest-tools" path="src/platform/container-guest-tools" revision="bccab5381237ecbde9e62f457408088e3c1a6206" upstream="refs/heads/master"/> |
| <project name="chromiumos/docs" path="docs" revision="18be589cba4ba9b8e279c7f42ce53d1f175bf2eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/graphyte" path="src/platform/graphyte" revision="10d607271aef6033e704ce55cabfef486fdd3211" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/bad_cl_detector" path="infra/bad_cl_detector" revision="08bb5589019bbaae1039240ce347cdc3ed05f43a" upstream="refs/heads/master"/> |
| <project groups="chromeos-admin" name="chromiumos/infra/ci_results_archiver" path="infra/ci_results_archiver" revision="4493ad78616152e22672ed245b72806c56cfef0d" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/cl_exonerator" path="infra/cl_exonerator" revision="2b776e5bd575c2373bcecc990057b6bbeaeba7b5" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/cl_status_viewer" path="infra/cl_status_viewer" revision="6bda7c611af03cb53db2afa190e0a81ce6d37169" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/distfiles_updater" path="infra/distfiles_updater" revision="2d1aa33972b2028d19a288baaacee9b2cd8644f7" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/dummies/general-sandbox" path="infra/dummies/general-sandbox" revision="ab009ffebb68a58f37779bddfba5f1a08ef174ae" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/dummies/merge-sandbox" path="infra/dummies/merge-sandbox" revision="651c1f3b89c112222f5dae2f79091421543dd4ee" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/logstock" path="infra/logstock" revision="ef7fe408b9feee9a3664b36f0176fcacd27bf703" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/lucifer" path="infra/lucifer" revision="d86f27c84317253bdcb7be1c23ef33aaa84cf896" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/proto" path="chromite/infra/proto" revision="8b42d3bfb5980f80fd5db12b2e2157d8bbcdf342" upstream="refs/heads/master"> |
| <annotation name="branch-mode" value="tot"/> |
| </project> |
| <project groups="chromeos-admin" name="chromiumos/infra/recipes" path="infra/recipes" revision="6a04bc6e43e8c4009410e199f4fd8da592b95450" upstream="refs/heads/master"> |
| <annotation name="branch-mode" value="tot"/> |
| </project> |
| <project groups="chromeos-admin,labtools" name="chromiumos/infra/skylab_inventory" path="infra/skylab_inventory" revision="f49a386349721336e9248acb5d67adb7f3a12939" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/suite_scheduler" path="infra/suite_scheduler" revision="781b34e79163a236b339c7a0011343056a010246" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/test_analyzer" path="infra/test_analyzer" revision="7b0a71303075b11ce506fe6c34477a139c02236e" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,chromeos-admin,labtools,sysmon,devserver" name="chromiumos/infra_virtualenv" path="infra_virtualenv" revision="ed74a599cd23c7ac90030330421127aa88ba30e8" upstream="refs/heads/master"/> |
| <project name="chromiumos/manifest" path="manifest" revision="32776ea77f7be2618856e8deb2b3fc2cd515180e" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="95d188f16353052f53d60c1f80abc278cd2c1cd3" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,labtools" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="d37627ade8d080e7810c65e3a4bc7b8a9b8e6ca8" sync-c="true" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,labtools" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="735e0a5ac48b748d45966164832f916c5024a650" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,labtools" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="19486d7fe26e5980ab41eeb2f09c5be197e02ebb" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/assets" path="src/platform/assets" revision="bab7377822fadd3c9b53744d90e4c7f4dd1131d2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="923ffb49d795da9abd67d440b011e6211a92fe44" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/battery_updater" path="src/platform/battery_updater" revision="32463c6de8e8c98d4b1711937bc7678afc121a85" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bisect-kit" path="src/platform/bisect-kit" revision="fd2ea5e021672637390ac3747aa9cbb6bbde7fc9" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bmpblk" path="src/platform/bmpblk" revision="2038f97359f79ecd202cc1a11294f4b6e4ab4ecf" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bootcache" path="src/platform/bootcache" revision="ebe3a0995e90026433ffc62b7aeed6cad1f28694" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/btsocket" path="src/platform/btsocket" revision="300354e5d74418c8e03737ca9029c64d9297a28d" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/cfm-device-monitor" path="src/platform/cfm-device-monitor" revision="b3ab7026704b6b7cf3f2f61e7a7347b3c3fd3dfd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chameleon" path="src/platform/chameleon" revision="3bc5a000f420cb8d823ac6e5f8b772173faaf4aa" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chromiumos-assets" path="src/platform/chromiumos-assets" revision="fd4e8eef335ceaca7adf53a83f5e13e00e09101c" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/cobble" path="src/platform/cobble" revision="3d2b9922e81cce898d4f09306563d3ca9d32c67e" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools" name="chromiumos/platform/crostestutils" path="src/platform/crostestutils" revision="7709ff2b7b3e3d7df9942cc51f7e7dd1c99c7549" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,labtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="6b80db6e123ce8e2537ad820295463b2d86ea038" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/crosvm" path="src/platform/crosvm" revision="bb340d9a94d48514cbe310d05e1ce539aae31264" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="b078fe268ccbbedaa3b383ab98e05ec913bc4cb4" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,devserver" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="4b08e71026b2052745d58140dc066449ddd7be10" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="b69aeca51481055c58780981d9e8aa1aef90491b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="8ed7891f35099bc9d5b8a4164b5ab847d5f1576f" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/ec" path="src/platform/ec" revision="8374923a60c8b63b7bb2c1823e4f5b6078544e44" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/experimental" path="src/platform/experimental" revision="bcc00ca58726d9cf774c56005715a5ee330da045" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/factory" path="src/platform/factory" revision="6f23f4864da023fe8258238901b1ecf83399733b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="602c47a5ff8d1d95808f87b6b5f9b0de5097d7ad" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/firmware" path="src/platform/firmware" revision="f6135987e0e846db867c1eb5bad817f5777383bc" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="755f3ca45df2291121aa8b8a031ca3b52e54d0ef" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="113de4bb26e228fd74c74cadb3a9a1272e11df5b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/glbench" path="src/platform/glbench" revision="b0595eb94d8c1950f0e8509a06921a035caba464" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/go-seccomp" path="src/platform/go-seccomp" revision="613458c0e3c589e52e7f093288ef1d2ba57a9ff7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/google-breakpad" path="src/third_party/breakpad" revision="c4b1ec1341369a10694374c62d2c2497f589418a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="eb4d97c66928980a21946e1ce3f62f93a378ed1e" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/inputcontrol" path="src/platform/inputcontrol" revision="8826acba1c4e13b6318ae6d1d4b49633d1b55aba" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/jabra_vold" path="src/platform/jabra_vold" revision="8830911158ae632b7626d0ebe33248e66ffaeef3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/libevdev" path="src/platform/libevdev" revision="23f8ea74685ea0a03be8649ca33d5664bc789393" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/microbenchmarks" path="src/platform/microbenchmarks" revision="518003bc070970f25b9ab97c0560d762846c5e65" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/minigbm" path="src/platform/minigbm" revision="1cbcbfd5f9908f694d3786b03d5a2bf0a5af6b90" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/moblab" path="src/platform/moblab" revision="3d73a0842368d012e0611a738de3f01a4023bf74" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="74b96e195d1c8a8f35bc9b183e8ea32f9776a3d8" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mttools" path="src/platform/mttools" revision="3c0e9c4a66f929e5752f5bf5fe45b1df5a0eb398" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/newblue" path="src/platform/newblue" revision="2dc4bf5e25aac67f56ec500bffb263d3f31f5a6f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/punybench" path="src/platform/punybench" revision="16bc496a97c027147453e7d675ae2f9147352b31" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tast" path="src/platform/tast" revision="1ee05bb6359ef64fac808b89913d769d48701966" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tast-tests" path="src/platform/tast-tests" revision="4c46a6370558296a27be9f50704c6a00d92a93af" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="bafba938ff65099158b04ca718b1e77a0e43c5c4" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="aafb953d89d152fb3e954017310ece41b5a4db62" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchbot" path="src/platform/touchbot" revision="9546ffbb37d5fef191ad1607eeb0b76a6f3a9872" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchpad-tests" path="src/platform/touchpad-tests" revision="8af3910ce3c674c6e32432fa3e793e31d2c2fe02" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/tpm" path="src/third_party/tpm" revision="0cba6cadd1bea1ce3717779201d594c4c9131dc2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm_lite" path="src/platform/tpm_lite" revision="db50af69b91bc1cffde13740c23aed72883fbc45" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tremplin" path="src/platform/tremplin" revision="4bb8e35efefe10b9fc82fa896478b026fced0a89" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/uboot-env" path="src/platform/uboot-env" revision="ab10366ee27959666b94a638858032c91c3c5e10" upstream="refs/heads/master"/> |
| <project groups="firmware,buildtools" name="chromiumos/platform/vboot_reference" path="src/platform/vboot_reference" revision="de5b8dff95811ba0bbe27c7f5cb7bb0269eab761" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vkbench" path="src/platform/vkbench" revision="13960bea358f67210b1902be4c108b9cab7e50c9" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="f0819c100986e6a5deceb86ffdc517b8d668e36b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="7da13f7e99160d4d9d2affd3b8eca5dcdec42967" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="2dd3d106bd58a967dca1551808c11f269741d9b0" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,labtools" name="chromiumos/repohooks" path="src/repohooks" revision="acfb18af36cf972b11974bb0cc103d38be0538c8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="f7a33e235022431a7cd7eefafb44ba808526b0bf" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/android_mtdutils" path="src/third_party/android_mtdutils" revision="9bcfc3ee238f16925e9aaa4573129784ebb397e7" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/arm-trusted-firmware" path="src/third_party/arm-trusted-firmware" revision="c33aa45f4400bc7c09fed1300bc59e0e70d36bd8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/atheros" path="src/third_party/atheros" revision="52a5bdaa8930c14ee42518354de3e5ec09911c6b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/atrusctl" path="src/third_party/atrusctl" revision="af9682236ee5a11e8900acc3f31165e91da2d95d" upstream="refs/heads/master"/> |
| <project groups="buildtools,labtools,devserver" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="a9e9369c4d5bd95d8411a1b751991016741495eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/aver-updater" path="src/third_party/aver-updater" revision="cf3337b0918e15755782d8f3b11691e04f1ddc40" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="30d4108f1662e60639a8a618e1ec9d8cfae2f0e4" upstream="refs/heads/chromeos-5.44"/> |
| <project groups="firmware" name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="6697fe6404055443d7c754b365907a0604f14111" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/broadcom" path="src/third_party/broadcom" revision="4070e7161f2f1a1a22027a744eb868500688f0b6" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/cbootimage" path="src/third_party/cbootimage" revision="b7d5b2d6a6dd05874d86ee900ff441d261f9034c" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="7e38583b4d7fad95decae4a40a3b1f575f880ea0" upstream="refs/heads/chromeos-2016.05"/> |
| <project groups="firmware" name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="678b4c4a81069bb6e10e2e59f5374b83d727cd2b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cros-adapta" path="src/third_party/cros-adapta" revision="eb6d8c1832b9181926df107faf41a80887fd982c" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/cryptoc" path="src/third_party/cryptoc" revision="b256f3941b8de4987d75eaa7df7bd8566cec2ef1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cups" path="src/third_party/cups" revision="c6054558bdb47735196f50cec16995d58c93bd2f" upstream="refs/heads/cups-2-2-8"/> |
| <project name="chromiumos/third_party/daisydog" path="src/third_party/daisydog" revision="5f4302621d8e011edbd83858b0c3183e29f842b5" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-cplusplus" path="src/third_party/dbus-c++" revision="98ffa268c972a79e9ea14872f2765626fd0c741d" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/edk2" revision="ab586ccd21556108662fbd80ab5a429143eac264" upstream="refs/heads/chromeos-2017.08"/> |
| <project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/cml/edk2/branch1" revision="49fa59e82e4c6ea798f65fc4e5948eae63ad6e07" upstream="refs/heads/chromeos-cml-branch1"/> |
| <project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/cnl/edk2" revision="f71a70e7a4c93a6143d7bad8ab0220a947679697" upstream="refs/heads/chromeos-cnl"/> |
| <project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/glk/edk2" revision="f71a70e7a4c93a6143d7bad8ab0220a947679697" upstream="refs/heads/chromeos-glk"/> |
| <project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/icl/edk2" revision="8df83bf3e30ada89fc0799859e3de25017dc93ac" upstream="refs/heads/chromeos-icl"/> |
| <project groups="firmware" name="chromiumos/third_party/em100" path="src/third_party/em100" revision="a621754a062430a2db3a53e6718a83dc8cec4684" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/fastrpc" path="src/third_party/fastrpc" revision="2ab40143cc017892b0b89f81c556cb4a80f70e8b" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/flashmap" path="src/third_party/flashmap" revision="274688eb2280dba7d1e0afe5a6a77c703624c43f" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/flashrom" path="src/third_party/flashrom" revision="46b1e496e2cc043d9fc815f899f324b6b2708d95" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/fwupd" path="src/third_party/fwupd" revision="62d946925a06791cdc54a98fc415081f478528d5" upstream="refs/heads/fwupd-1.2.5"/> |
| <project groups="labtools" name="chromiumos/third_party/hdctools" path="src/third_party/hdctools" revision="97d8631003a740bc9efda59c706e196f99df0742" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="f7f2b290fa45e9165da8f95c45edb0d96d041738" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant-2.6" revision="63bc633f00b4dd952802b145cb247cb2e1b51650" upstream="refs/heads/wpa_supplicant-2.6"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant-2.8" revision="6a2e0248bd94e5d27ce74f9950a87298b86949e4" upstream="refs/heads/wpa_supplicant-2.8"/> |
| <project name="chromiumos/third_party/huddly-updater" path="src/third_party/huddly-updater" revision="16cef48eb9db1c734083496890d6d0480ea65a95" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.8" revision="9304733ce7e720c06db26fdc31c80c24cfd81e9b" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="441a28be21f09998848a5a5867a6f79cb31ec91c" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="43807030c1b090e2c297e093ad525da4c9b7e9a3" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="5bfb08636e979a52e86428fe2dc098b035bcbdb4" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.4" revision="09aa33310ac418e976e414c0d238d9cda4975704" upstream="refs/heads/chromeos-4.4"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.14" revision="b65ce54943d03df0bd1a15d4867f3659ab7950ff" upstream="refs/heads/chromeos-4.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.14-mistral" revision="07e822e7809e3baad0a1f4e95f57adad2f9464f7" upstream="refs/heads/chromeos-4.14-mistral"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.14-gw" revision="50332374cb85768f23683db30bb0ccf56af626a4" upstream="refs/heads/chromeos-4.14-gw"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.19" revision="2b4dc57b38c378d7eb44b763a19f940eb43b3049" upstream="refs/heads/chromeos-4.19"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="d41e9e578eef76ebd804f3361eb67fce1009c2b4" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/kvmtool" path="src/third_party/kvmtool" revision="1b159b990afd33c0c2e3b47ebda6dd5cc793dd92" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libc-bench" path="src/third_party/libc-bench" revision="76793dd4b09191a78a78180012718e72d792717f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libcamera" path="src/third_party/libcamera" revision="b2b3599b5b0673901bbce958bd9802b9d6313fcf" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libdrm" path="src/third_party/libdrm" revision="b7a7a90336fbb19efb3f91f92b5d964b0dfb7ec2" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libiio" path="src/third_party/libiio" revision="8539d5dcf2d04cfc1985e3272fb20b3109ebb492" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="6ab7fcefd89faaffc53db0cbe7052dcab9d0c4d8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="7183ca5142b8246959643edf49e78ea1d3b0d01a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqrtr" path="src/third_party/libqrtr" revision="1604a9567beda30fb5d8fd532c0ec8366da8fbbb" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libscrypt" path="src/third_party/libscrypt" revision="b45c53f9418a6eff2c8ed98703a55f96029304b1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libsigrok" path="src/third_party/libsigrok" revision="199fe31115c76231746f5953271795d58679561c" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrok-cli" path="src/third_party/sigrok-cli" revision="c9edfa218e5a5972531b6f4a3ece8d33a44ae1b5" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrokdecode" path="src/third_party/libsigrokdecode" revision="3279c2825684c7009775b731d0a9e37815778282" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libv4lplugins" path="src/third_party/libv4lplugins" revision="aac7c20e25b5374fd644ddc7b26f088e71c3bf51" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/linux-firmware" path="src/third_party/linux-firmware" revision="d759a79cc06d65ba27340ef4af281e843824ad50" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/logitech-updater" path="src/third_party/logitech-updater" revision="658d14909e3231dddedebbd769db36d7a9f6d784" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="08733aa7d62b171c667d3eb7e299aa7345053fa9" upstream="refs/heads/chromeos-20150119"/> |
| <project name="chromiumos/third_party/marvell" path="src/third_party/marvell" revision="4773273dec5ea6ff8151459a6b63b51dc4bc164d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="1d363d440f261fbadc1db3c17acc514b7130d505" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-debian" revision="1d814714ba7051a034131d48961e631214f69708" upstream="refs/heads/debian"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-freedreno" revision="1619f208834544e57349b29bb1f3f1ec98ca0cbc" upstream="refs/heads/chromeos-freedreno"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-img" revision="129178893b2260df22db96327c5ca9c2ce7db046" upstream="refs/heads/mesa-img"/> |
| <project name="chromiumos/third_party/mimo-updater" path="src/third_party/mimo-updater" revision="2ee2d98e2cce58d2ec376aa5a90805399df70505" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mmc-utils" path="src/third_party/mmc-utils" revision="1c55306a49b32bbb8c65e1e5e9d630f6720a6810" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="5b752047977b69618f1b31bd08fd38de6f4f5ba3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/nfs-ganesha" path="src/third_party/nfs-ganesha" revision="165395bf01548d8a0135357ca4c222b9c0c0acaa" upstream="refs/heads/V2.3-stable"/> |
| <project name="chromiumos/third_party/ntirpc" path="src/third_party/ntirpc" revision="a9fc54d636fc3e5b5f0918769a2e5343c5f0d823" upstream="refs/heads/V1.3.3-cros"/> |
| <project name="chromiumos/third_party/portage_tool" path="src/third_party/portage_tool" revision="4489a466b6c0c7eb370e1390d2ce178900bce113" upstream="refs/heads/chromeos-2.3.49"/> |
| <project groups="minilayout,firmware,buildtools" name="chromiumos/third_party/pyelftools" path="chromite/third_party/pyelftools" revision="af64f6c7b19cdb84226161dd3742a13fd7974cc3" upstream="refs/heads/master-0.22"/> |
| <project name="chromiumos/third_party/rootdev" path="src/third_party/rootdev" revision="8dc336a991e5494e6cc9a0094778fee67f22ed6c" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/seabios" path="src/third_party/seabios" revision="3004147dd3707e600772ec6c5d37beac7f4b8eb4" upstream="refs/heads/chromeos-2014.11.03"/> |
| <project name="chromiumos/third_party/sis-updater" path="src/third_party/sis-updater" revision="4066f05ebae55958e3d193f9177c310b1d480886" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/sound-open-firmware" path="src/third_party/sound-open-firmware" revision="2f3a03f1b0ef5b00e8de4fa5079fb2885fcf66c2" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/sysbios" path="src/third_party/sysbios" revision="33e1db34b8162de72a5e9bbbc44e6bce38978396" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="6d6944a9924a45367b8f1667bad93ef714e64ef6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/toolchain-utils" path="src/third_party/toolchain-utils" revision="71916491b62a7a1dd3ccbcc0c2cef7df5dc72e0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm-emulator" path="src/third_party/tpm-emulator" revision="310a21ef24ace14b4d6e8095172445494f54ff25" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/third_party/tpm2" path="src/third_party/tpm2" revision="1dba349a7b272071d613869adaaef7bd576ae0c2" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="70607d705f63f54a9f6df3e184c685168df23881" upstream="refs/heads/master-0.3.13"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/files" revision="8084afd71b2989bbb1988488fcb1764202f79b2b" upstream="refs/heads/chromeos-v2018.09"/> |
| <project name="chromiumos/third_party/virglrenderer" path="src/third_party/virglrenderer" revision="ab3640c0858df496b5d97f075a2e26c23bdfab98" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/virtual-usb-printer" path="src/third_party/virtual-usb-printer" revision="3aa8acfc3fd2902cfb158beb1e0e85f7bf7bf88a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/webrtc-apm" path="src/third_party/webrtc-apm" revision="3e710eb8fd54f22e064cd0eb98ddd256f771d38a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/whining" path="src/third_party/whining" revision="c325abd3eff318af433a1a5667f5d2745f893945" upstream="refs/heads/master"/> |
| <project name="external/git.kernel.org/fs/xfs/xfstests-dev" path="src/third_party/xfstests" revision="3a82f23e450c2447d43d487e5a35bf6a5f313045" upstream="refs/heads/master"/> |
| <project groups="buildtools,chromeos-admin,firmware,labtools,minilayout" name="infra/luci/client-py" path="chromite/third_party/swarming.client" remote="chromium" revision="34b20305c7a69eb89e1abd5e2a94708db999f0a9"/> |
| <project name="linux-syscall-support" path="src/third_party/breakpad/src/third_party/lss" revision="a89bf7903f3169e6bc7b8efc10a73a7571de21cf"/> |
| <project name="platform/external/bsdiff" path="src/aosp/external/bsdiff" remote="aosp" revision="1a313bad729068bfd60f9f86c5769671bc652b53" upstream="refs/heads/master"/> |
| <project name="platform/external/libcxx" path="src/aosp/external/libcxx" remote="aosp" revision="81231c9ecd77a2f6492cf87807392434eb83134e" upstream="refs/heads/master"/> |
| <project name="platform/external/libcxxabi" path="src/aosp/external/libcxxabi" remote="aosp" revision="ebe828e0f9ec7cbaa7a8173703bf7a0457629a60" upstream="refs/heads/master"/> |
| <project name="platform/external/libunwind_llvm" path="src/aosp/external/libunwind_llvm" remote="aosp" revision="d88b1fc62511d02ee2021628af7c571528a09b8c" upstream="refs/heads/master"/> |
| <project name="platform/external/minijail" path="src/aosp/external/minijail" remote="aosp" revision="1f5d095bb0d2225343731bd402026ed15e4a44e0" upstream="refs/heads/master"/> |
| <project name="platform/external/puffin" path="src/aosp/external/puffin" remote="aosp" revision="170cb8d77faed2c7a05e527e9e2923f2ae3587dd" upstream="refs/heads/master"/> |
| <project name="platform/system/keymaster" path="src/aosp/system/keymaster" remote="aosp" revision="058085425b50fedc1f614c3479287337aa129eb7" upstream="refs/heads/master"/> |
| <project name="toolchain/binutils" path="src/aosp/toolchain/binutils" remote="aosp" revision="cce69c1b1bfc46de5e1cdd4923f87215c0edb884"/> |
| <project name="toolchain/gcc" path="src/aosp/toolchain/gcc" remote="aosp" revision="ac6128e0a17a52f011797f33ac3e7d6273a9368d"/> |
| <project name="weave/libweave" path="src/weave/libweave" revision="6c12d9355b426313bed15f3164bea8e96d33cd6e" upstream="refs/heads/master"/> |
| <repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/> |
| <pending_commit branch="chromeos-2016.05" change_id="Ia4d976e6965947334b048d0b3236ce4454bb1a13" commit="3baaa409b2401b7dc3934a062667063ddd7eee7f" commit_message="UPSTREAM: mainboard/hp/z220_sff_workstation: remove unused header file BUG=none BRANCH=none TEST=none Change-Id: Ia4d976e6965947334b048d0b3236ce4454bb1a13 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 092fa8bba8c1f6ae0be2afd27b9a113e01b244c8 Original-Change-Id: I4c780afaccd604a1bf4da67eea713f809744ddb2 Original-Signed-off-by: Felix Held <felix-coreboot@felixheld.de> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33349 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: HAOUAS Elyes <ehaouas@noos.fr> Original-Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-on: https://chromium-review.googlesource.com/1658051 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658051" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/51/1658051/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I44da87c8b7ade1b11d80beffb40741529d74bea7" commit="afba480893402fd7b223771c34f2c8fb41a19e46" commit_message="UPSTREAM: cbfs_spi: Enable speed logging by default for BIOS_DEBUG The SPI transfer speed logging in cbfs_spi is super useful, doesn't get in the way (just adding one line per stage, essentially) and should have no notable overhead. Let's enable it by default for the BIOS_DEBUG log level rather than having to recompile to get it. Also fix an issue with building this code on MIPS due to lack of 64-bit division primitives. (This means MIPS and arm32 board may display incorrect results when reading more than 4MB in a single transfer, which sounds very unlikely.) BUG=none BRANCH=none TEST=none Change-Id: I44da87c8b7ade1b11d80beffb40741529d74bea7 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 8dcf24fcbf5746693ae0227e9cdfb486efb4907e Original-Change-Id: I03c77938afe01fdcecf917e8c4c25cc29cdc764e Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33281 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-by: Simon Glass <sjg@chromium.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658052 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658052" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/52/1658052/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Ia8d7f7a005eb9ee8a24c5a74828da6fbee4f24db" commit="89a1673f59dffa7e267c1dd882613759323cee9b" commit_message="UPSTREAM: spi_flash: gigadevice: Adopt Winbond chip info structure This patch changes the Gigadevice SPI flash driver to adopt the same structure packing improvements for the hardcoded parameters of individual chips that was implemented for Winbond last year. This cuts the size of the hardcoded info nearly in half and should save us a few hundred bytes in every stage. BUG=none BRANCH=none TEST=none Change-Id: Ia8d7f7a005eb9ee8a24c5a74828da6fbee4f24db Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 381c35c7f901608277f00477e04977bf938b0b59 Original-Change-Id: I9910dcb9b649f51b317f3f8fcba49e5e893f67d2 Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33285 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658053 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658053" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/53/1658053/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Ieb09eaf57fe4d44ef9e5a1b601f75325759ba7d7" commit="96b89691396c3902115e4641a5be0ba645ef48ef" commit_message="UPSTREAM: spi_flash: Make .read() callback optional All SPI flash chip drivers currently in coreboot use the generic read functions (spi_flash_cmd_read_fast()/_slow()) as their read callback. The only use case for specialized read callbacks we have left is with specialized flash controllers like Intel fast_spi (which sort of impersonate the flash chip driver by implementing their own probe function). This patch unifies the behavior for all normal flash drivers by making the read callback optional and letting them all fall back to a default read implementation that handles normal fast/slow reading. Most of the drivers used to install the respective callback after checking CONFIG_SPI_FLASH_NO_FAST_READ, but some hardcoded either slow or fast writes. I have found no indications for why this is and spot-checked datasheets for affected vendors to make sure they all support both commands, so I assume this is just some old inaccuracy rather than important differences that need preserving. (Please yell if you disagree.) Also take the opportunity to refactor some of the common spi_flash.c code a bit because I felt there are too many nested functions that don't really do enough on their own, and centralizing stuff a bit should make it easier to follow the code flow. (Some of this is in preparation for the next patch.) BUG=none BRANCH=none TEST=none Change-Id: Ieb09eaf57fe4d44ef9e5a1b601f75325759ba7d7 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 1b7f99bd6b52e3fd03653dca80af3faf6e7e8852 Original-Change-Id: I2096a3ce619767b41b1b0c0c2b8e95b2bd90a419 Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33282 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Arthur Heymans <arthur@aheymans.xyz> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1658054 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658054" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/54/1658054/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I6c0d2d9f018b9950a154295802ede6acfff8b1fe" commit="2292ba0a904843ee03b152270914b381d43611ec" commit_message="UPSTREAM: spi_flash: Add Dual SPI support This patch adds support to read SPI flash in Dual SPI mode, where both MISO and MOSI lines are used for output mode (specifically Fast Read Dual Output (0x3b) where the command is still sent normally, not Fast Read Dual I/O (0xbb) whose additional benefit should be extremely marginal for our use cases but which would be more complicated to implement). This feature needs to be supported by both the flash chip and the controller, so we add a new dual_spi flag (and a new flags field to hold it) to the spi_flash structure and a new optional xfer_dual() function pointer to the spi_ctrlr structure. When both are provided, Dual SPI mode is used automatically, otherwise things work as before. This patch only adds the dual_spi flag exemplary to all Winbond and Gigadevice chips, other vendors need to be added as needed. BUG=none BRANCH=none TEST=none Change-Id: I6c0d2d9f018b9950a154295802ede6acfff8b1fe Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 99e45ceb35ff9a4c48e516e6d005ebfae54b6591 Original-Change-Id: Ic6808224c99af32b6c5c43054135c8f4c03c1feb Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33283 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658055 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658055" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/55/1658055/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Id8189bf44ce51c88723ca3465ab8acaf3a6dcd7e" commit="f35df94f1d59660a9d62fbcad3371afb3da9674b" commit_message="UPSTREAM: sdm845: qspi: Add Dual SPI support This patch adds support for the Dual SPI feature (SDR 2-bit in Qualcomm terminology) to the QSPI controller. BUG=none BRANCH=none TEST=none Change-Id: Id8189bf44ce51c88723ca3465ab8acaf3a6dcd7e Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 127a55e91d46623f700ba39f2679e3606ed0b2fb Original-Change-Id: I7aed2ccd9627f5de5dd760b418f74d56d2c031d3 Original-Signed-off-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33284 Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/1658056 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658056" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/56/1658056/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Ia732e13daee63f6f96aefaae0b316692f491bd12" commit="161b4d457e6f5f231bddd834e8f107dc71cbe12b" commit_message="UPSTREAM: mb/google/poppy/variants/nami: remove redundant break Break never comes after return, remove it. BUG=N/A BRANCH=firmware-nami-10775.108.B TEST=N/A Change-Id: Ia732e13daee63f6f96aefaae0b316692f491bd12 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: f4035bffb1bc499cf4fe725f8318385e46ff73f6 Original-Signed-off-by: Eric Lai <ericr_lai@compal.corp-partner.google.com> Original-Change-Id: I005918d6a04cd21df496dea0f2cb1ed6108675af Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33299 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Duncan Laurie <dlaurie@chromium.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658057 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658057" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/57/1658057/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I9b225162439f11a47f842128a80c6cb419e9cf76" commit="41ff93aecf789d78d36b46d54f6fa405a216e711" commit_message="UPSTREAM: mb/google/sarien/variants/arcada: Update thermal configuration for DPTF Update dptf for arcada DVT2. BUG=b:123924662 TEST=Built and tested on arcada system Change-Id: I9b225162439f11a47f842128a80c6cb419e9cf76 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 1cf5ea5f1db6f780cd6da052c615a920c7201462 Original-Signed-off-by: Mike Hsieh <mike_hsieh@wistron.corp-partner.google.com> Original-Change-Id: I302b7cd4c7e0579acb5482800241b5229cfc49f7 Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33360 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Sumeet R Pawnikar <sumeet.r.pawnikar@intel.com> Original-Reviewed-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1658058 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658058" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/58/1658058/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I948bafd9e41a573e4ad0de98bed0cf74ef4b9298" commit="90b2d8a6b46e2bd2880827027723b906bfed4340" commit_message="UPSTREAM: soc/amd/common: Add errors for invalid AcpiMmio access Add a method for the soc/amd/<product> to indicate what AcpiMmio ranges are supported. Induce a build error if soc or mainboard code is added which attempts to use an unsupported block. This patch attempts to dissuade accessing unsupported blocks without requiring the complexity of structures or reinitializing at the beginning of a new stage. TEST=boot grunt, force build errors by removing blocks in iomap.h BUG=b:131682806 Change-Id: I948bafd9e41a573e4ad0de98bed0cf74ef4b9298 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 2395917adfd267a737beb38285a8e689b27235aa Original-Change-Id: I2121df108fd3caf07e5588bc3201bcdd8dcaaa00 Original-Signed-off-by: Marshall Dawson <marshalldawson3rd@gmail.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/32934 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Martin Roth <martinroth@google.com> Original-Reviewed-by: Richard Spiegel <richard.spiegel@silverbackltd.com> Reviewed-on: https://chromium-review.googlesource.com/1658059 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658059" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/59/1658059/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Ib3947a4f3b2a60ee1fda6f3ba50f4fd708a89b66" commit="609c3d8d91ddb9243dd8ec28252df1500d70717e" commit_message="UPSTREAM: Rampayload: Able to build coreboot without ramstage This patch removes all possible dependencies in order to build platform with CONFIG_RAMPAYLOAD enable(without ramstage). A. Create coreboot separate stage kconfigs This patch creates seperate stage configs as below 1. HAVE_BOOTBLOCK 2. HAVE_VERSTAGE 3. HAVE_ROMSTAGE 4. HAVE_POSTCAR 5. HAVE_RAMSTAGE B. Also ensures below kconfigs are aligned with correct stage configs 1. COMPRESS_RAMSTAGE and RELOCATABLE_RAMSTAGE are now enable if CONFIG_HAVE_RAMSTAGE is selected. 2. COMPRESS_BOOTBLOCK will enable if CONFIG_HAVE_BOOTBLOCK is set 3. COMPRESS_PRERAM_STAGES will enable if CONFIG_HAVE_VERSTAGE || CONFIG_HAVE_ROMSTAGE is selected. C. Also fix compilation issue with !CONFIG_HAVE_RAMSTAGE On x86 platform: Case 1: ramstage do exist: CONFIG_HAVE_RAMSTAGE=1 >> rmodules_$(ARCH-ramstage-y) will evaluate as rmodules_x86_32 Case 2: ramstage doesn't exist: CONFIG_HAVE_RAMSTAGE=0 >> rmodules_$(ARCH-ramstage-y) will evaluate as rmodules_ This patch fixes Case 2 usecase where platform doesn't select CONFIG_HAVE_RAMSTAGE. Also add option to create sipi_vector.manual based on $(TARGET_STAGE) variable. $(TARGET_STAGE)=ramstage if user selects CONFIG_HAVE_RAMSTAGE $(TARGET_STAGE)=postcar if user selects CONFIG_RAMPAYLOAD BUG=none BRANCH=none TEST=none Change-Id: Ib3947a4f3b2a60ee1fda6f3ba50f4fd708a89b66 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: b5962a934a4dae3d84590dc8ef290f5fa8fec34b Original-Change-Id: I0f7e4174619016c5a54c28bedd52699df417a5b7 Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33142 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1658060 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658060" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/60/1658060/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Ifb5b4899c64a10655a6edf5bc1df0b658e38adb0" commit="7e931ed4cdef9d2ff59a919b08a83c75e1b6fe3f" commit_message="UPSTREAM: console: Make die() and friends variadic die() currently only accepts a fixed message string, which is rather inconvenient when there is extra information that would be helpful to print in the error message. This currently requires an extra call to printk(), which is somewhat awkward: printk(BIOS_EMERG, "Bad table, opcode %d at %d", id, i); die(""); // what do I say here? die() already has a printk() inside it to print the error message, so let's just make it variadic to combine the two. die("Bad table, opcode %d at %d", id, i); // much better Forwarding variadic arguments from one function to another is rather tricky, so die_with_post_code() is redefined as a variadic macro instead. BUG=none BRANCH=none TEST=none Change-Id: Ifb5b4899c64a10655a6edf5bc1df0b658e38adb0 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 913437e8a268130b7fbfb9d6d366c42de4f681be Original-Change-Id: I28b9eac32899a1aa89e086e0d3889b75459581aa Original-Signed-off-by: Jacob Garber <jgarber1@ualberta.ca> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33153 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Martin Roth <martinroth@google.com> Original-Reviewed-by: Keith Short <keithshort@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1658061 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658061" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/61/1658061/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I7eecc85e28fd73a5410665c07e06f17e798fadef" commit="9700903cc0c7b94f83181c55146ed0cc2ebab33c" commit_message="UPSTREAM: console: Allow using vprintk() with disabled console The prototype of vprintk() is currently declared unconditionally, which prevents it from being used in situations where the console is disabled. The code will compile correctly, but not link, since the definition in console.c isn't being provided. This adds a shim around the declaration so that, like printk(), a call to vprintk() in this situation will expand to a no-op function instead. BUG=none BRANCH=none TEST=none Change-Id: I7eecc85e28fd73a5410665c07e06f17e798fadef Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: deb99af8a1bff0ca66cf5764570d5f8e2033039b Original-Change-Id: Ib4a9aa96a5b9dbb9b937ff45854bf6a407938b37 Original-Signed-off-by: Jacob Garber <jgarber1@ualberta.ca> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33181 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Martin Roth <martinroth@google.com> Original-Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-on: https://chromium-review.googlesource.com/1658062 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658062" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/62/1658062/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I5101bcd3fbc0f90b2d7a4fef62dbe70ad890b789" commit="0e1158c22730cf6e10bf8d8db5cc040aa5a6048a" commit_message="UPSTREAM: mainboard/google/kahlee: Reduce VRAM to 16MB It was determined through testing that 16MB of reserved VRAM is sufficient. Additional RAM for the graphics driver is allocated out of system memory. BUG=b:123579702 TEST=Boot Grunt, watch VRAM usage with graphics driver logging. Change-Id: I5101bcd3fbc0f90b2d7a4fef62dbe70ad890b789 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 87dcd0061af48752469a77824715101180ab259e Original-Change-Id: I44b640f015b45c0dc3d701929549f3a1082a9268 Original-Signed-off-by: Martin Roth <martinroth@google.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33368 Original-Reviewed-by: Arthur Heymans <arthur@aheymans.xyz> Original-Reviewed-by: Raul Rangel <rrangel@chromium.org> Original-Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/1658063 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658063" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/63/1658063/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Icc30afd7ea53463415a0dff6dc6be97320943dc8" commit="301e5a969f4754c78068a40142e1d99455def168" commit_message="UPSTREAM: Revert "mb/google/poppy/variants/atlas: enable NVMe" This reverts commit 41979d862a972375d6800afdf2b8b52d408fd220. Reason for revert: NVMe is no longer supported. BUG=b:134752066 Change-Id: Icc30afd7ea53463415a0dff6dc6be97320943dc8 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 70ca84d6e7a2a591ca32c14ca927d9c636ec75d0 Original-Change-Id: I95f2e5f5efe2417700d458f0efd3c793fd8ce8c3 Original-Signed-off-by: Caveh Jalali <caveh@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33307 Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Original-Reviewed-by: Bob Moragues <moragues@google.com> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/1658064 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658064" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/64/1658064/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="If319f27a7a92a6b2a3ed5404074e341578730fc4" commit="b9e26046f3efc3d8af3a61aff23810968c310567" commit_message="UPSTREAM: mb/google/hatch: Disable dynamic clock gating for cr50's GPIO Disable dynamic clock gating for the community cr50's IRQ lives on. That IRQ is pulsed very quickly, and with clock gating enabled pulses tend to be missed. This is expecially true on the default 0.0.22 firmware that cr50 comes with out of the factory. BUG=b:130764684 b:130338605 BRANCH=None TEST=Boot hatch with cr50 "intap" firmware that can vary the pulse width, observe that even with sub-microsecond pulses no IRQs are missed. Change-Id: If319f27a7a92a6b2a3ed5404074e341578730fc4 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: b5bea526ec80c0aeccd78a0ece6ac091aa512b54 Original-Change-Id: I34d14fb7cc97e33eecfda2c99cc53a541c87662d Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Signed-off-by: Evan Green <evgreen@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33326 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658065 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658065" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/65/1658065/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Iba9927073dadb06b80c7406389b4491358627e15" commit="0fab3818715c2cd82985bc304a85603b241932e0" commit_message="UPSTREAM: vboot: recovery path should finalize work context Recovery path should finalize work context, and trim vboot_working_data buffer_size. Otherwise, depthcharge ingests the full 12 KB workbuf in recovery path. BUG=chromium:972528, b:134893812 TEST=Build with vboot_reference CL:1584488. Check that USB disks are properly verified in recovery path. BRANCH=none Change-Id: Iba9927073dadb06b80c7406389b4491358627e15 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: ba50e4885fd68579ec76a149d28b0b9605381d7e Original-Change-Id: Icf2600d2eb5d846a26aec35a153946dd2f7f128c Original-Signed-off-by: Joel Kitching <kitching@google.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33358 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Hung-Te Lin <hungte@chromium.org> Original-Reviewed-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1658066 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658066" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/66/1658066/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Icd040e4a3b0a9fa5a5bb24ac4e6b47c54abf51c5" commit="82e4e3b3b2d356d5549d713fa1bc356bfcb2defc" commit_message="UPSTREAM: {drivers,soc/intel/braswell}: Implement C_ENVIRONMENT_BOOTBLOCK support No C_ENVIRONMENT_BOOTBLOCK support for Braswell is available. Enable support and add required files for the Braswell Bootblock in C. The next changes are made support C_ENVIRONMENT_BOOTBLOCK: - Add car_stage_entry() function bootblock-c_entry() functions. - Specify config DCACHE_BSP_STACK_SIZE and C_ENV_BOOTBLOCK_SIZE. - Add bootblock_c_entry(). - Move init from car_soc_XXX_console_init() to bootblock_soc_XXX_Init() Removed the unused cache_as_ram_main() and weak car_XXX_XXX_console_init() BUG=NA TEST=Booting Embedded Linux on Facebook FBG-1701 Building Google Banos Change-Id: Icd040e4a3b0a9fa5a5bb24ac4e6b47c54abf51c5 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 4e0ec592553fd94e14a239eeb05ba9ccb668b814 Original-Change-Id: Iab48ad72f1514c93f20d70db5ef4fd8fa2383e8c Original-Signed-off-by: Frans Hendriks <fhendriks@eltan.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/29662 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-on: https://chromium-review.googlesource.com/1658067 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658067" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/67/1658067/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I2e297b2a6221a54e42ab90d693947595c1ba0c90" commit="aeeebcf655be3c28a75674b6e34118154301cb4b" commit_message="UPSTREAM: qcom: Add i2c driver Add i2c driver in coreboot. BUG=none BRANCH=none TEST=none Change-Id: I2e297b2a6221a54e42ab90d693947595c1ba0c90 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 58ed173a2c8c42bf9d074e026ecedad14ef42f90 Original-Change-Id: I3d39d0325718fc5dd60da42eb2b87dcc4429bfc2 Original-Signed-off-by: Prudhvi Yarlagadda <pyarlaga@codeaurora.org> Original-Signed-off-by: Nitheesh Sekar <nsekar@codeaurora.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/32546 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658108 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658108" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/08/1658108/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I9a9396158c483c6f2b527c14c013927e155fd15d" commit="7b374ec7d6315062ea1078888ccdafdc8a4dc5a0" commit_message="UPSTREAM: mb/google/octopus: make new targets have DRAM part in CBI by default All new targets utilizing octopus mainboard support default to always using DRAM_PART_NUM_IN_CBI. This allows easier addition of new targets. BUG=b:132668378 BRANCH=octopus Change-Id: I9a9396158c483c6f2b527c14c013927e155fd15d Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 702d2364bd6aef6871201fc324534c2695e1a632 Original-Change-Id: Idb136aa960260abe1657b16ded02a7dfb63c6849 Original-Signed-off-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33370 Original-Reviewed-by: Justin TerAvest <teravest@chromium.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Original-Reviewed-by: Kevin Chiu <Kevin.Chiu@quantatw.com> Original-Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/1658109 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658109" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/09/1658109/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I94398ea94d5ae374ad11b674bd23faf20a7896d5" commit="53d3c89deb409133d10521f6e79994659d55a0e8" commit_message="UPSTREAM: libpayload: Add USB support to mistral config BUG=none BRANCH=none TEST=none Change-Id: I94398ea94d5ae374ad11b674bd23faf20a7896d5 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 8a70918b8a78d8d5cd27e830cc4ae496b10d4f32 Original-Change-Id: I2ef42f7d607eec6166d762ad71c0d9540906589d Original-Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33259 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Original-Reviewed-by: SANTHOSH JANARDHANA HASSAN <sahassan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658110 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658110" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/10/1658110/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I579c28db14811549649433a41dc1bd244d055631" commit="1cbe7d32d9e617c0deae07d966157d9c69f21a20" commit_message="UPSTREAM: soc/intel/icelake: Replace PCI device LPC to ESPI as per EDS As per Icelake EDS PCI device B:D:F (0:0x1f:0) referred as ESPI, hence modify SoC code to reflect the same. This patch replaces all SoC specific PCI LPC references with ESPI except anything that touches intel common code block. BUG=none BRANCH=none TEST=none Change-Id: I579c28db14811549649433a41dc1bd244d055631 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 3d152ac388fa43b4c3d1bfeedcb6a40f1479ace3 Original-Change-Id: I4990ea6d9b7b4c0eac2b3eea559f5469f086e827 Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33190 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Original-Reviewed-by: Lean Sheng Tan <lean.sheng.tan@intel.com> Reviewed-on: https://chromium-review.googlesource.com/1658111 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658111" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/11/1658111/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="Ia8c0ab94f52fb7f2cbf485a4733e1d8cc9cd3493" commit="296f1f31389984e7546ed6d3a283b113ba26c2bc" commit_message="UPSTREAM: soc/intel/{cml, whl}: Add option to skip HECI disable in SMM This patch provides an additional option to skip HECI function disabling using SMM mode for WHL and CML platform, where FSP has dedicated UPD to make HECI function disable. User to select HECI_DISABLE_USING_SMM if FSP doesn't provided dedicated UPD. Right now CNL and ICL platform will use HECI_DISABLE_USING_SMM kconfig to make HECI disable and WHL/CML has to rely on FSP to make HECI disable. BUG=none BRANCH=none TEST=none Change-Id: Ia8c0ab94f52fb7f2cbf485a4733e1d8cc9cd3493 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: a0368a0950bbd346b816c4397cfe9e86617d4f77 Original-Change-Id: If3b064f3c32877235916f966a01beb525156d188 Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33193 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Original-Reviewed-by: Nico Huber <nico.h@gmx.de> Reviewed-on: https://chromium-review.googlesource.com/1658112 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658112" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/12/1658112/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I4bb50846cca8b98bfacfb2f053d48a667fd5c4e0" commit="8f48e31961d311e949a8de691e1ed0020e78a15b" commit_message="UPSTREAM: mb/google/{hatch, sarien, arcada}: Make HECI1 chip config disable This patch is not actually disabling HECI1 as it requires a dedicated FSP UPD for WHL/CML SoC code to set this HECI1 chip config. BUG=none BRANCH=none TEST=none Change-Id: I4bb50846cca8b98bfacfb2f053d48a667fd5c4e0 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 5e5167ed04082e0fe63db865382dc2021877ce3c Original-Change-Id: Ia88f3315a9dc3365d0acc13ed887e7c596c97c91 Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33194 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658113 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658113" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/13/1658113/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I2c7ff87ad4922d2c248673f86b80eacc4c5b2803" commit="d76757b621f3f660d419d19a8c60a08fa397d49a" commit_message="UPSTREAM: stage_cache: Make empty inline function if CONFIG_NO_STAGE_CACHE enable This patch removes CONFIG_NO_STAGE_CACHE check from caller function and add empty inline function incase CONFIG_NO_STAGE_CACHE is enable. BUG=none BRANCH=none TEST=none Change-Id: I2c7ff87ad4922d2c248673f86b80eacc4c5b2803 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 90f750bbf0309bdf038a5af9f85aba323251072d Original-Change-Id: I8e10ef2d261f9b204cecbeae6f65fda037753534 Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/33394 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/1658114 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658114" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/14/1658114/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2016.05" change_id="I2c26e63742687c1c83ee36c3c6eab65a1c6e85b7" commit="75f4950124887ce91850bc1bcc2b8beab8df9343" commit_message="UPSTREAM: Set ENV_PAYLOAD_LOADER to ENV_POSTCAR when CONFIG_RAMPAYLOAD is enabled BUG=none BRANCH=none TEST=none Change-Id: I2c26e63742687c1c83ee36c3c6eab65a1c6e85b7 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 6302203fb439a2d87566cc3e107359da41ce0560 Original-Change-Id: I416c74ea83ee68370bbeb53834054bcb18e631e1 Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/32751 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: ron minnich <rminnich@gmail.com> Reviewed-on: https://chromium-review.googlesource.com/1658115 Tested-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="1658115" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/15/1658115/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ibe1842b5b6bf4eeca7cd59412686d65f7d7303b6" commit="2986199e4e7e6aa471d69a2c9e9fcafc02d012c2" commit_message="nebraska: Remove 'name' from json file The name is the payload file's name. However, if the payload file changes after the paygen, then one should modify its json file too to reflect that. But that coupling is not necessary, because we can easily assume that for a payload with name 'foo-payload.bin', its json file is 'foo-payload.bin.json'. Hence, the payload name can be drived from the json file itself and no need to modify the content of the json file. Just rename both files accordingly. BUG=chromium:920404 TEST=unittest Change-Id: Ibe1842b5b6bf4eeca7cd59412686d65f7d7303b6 Reviewed-on: https://chromium-review.googlesource.com/1595105 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1595105" owner_email="ahassani@chromium.org" pass_count="0" patch_number="7" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/05/1595105/7" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3db5725e179483acc83617e6014370b36eb8ccb4" commit="4633cd3d29b7953095ffd484bbbe16e035ff6e95" commit_message="nebraska: Move AppData-Request matching logic to Request object Let's keep the AppData object just a simple dict/struct and move the request matching logic into Request object itself. BUG=chromium:920404 TEST=unittest Change-Id: I3db5725e179483acc83617e6014370b36eb8ccb4 Reviewed-on: https://chromium-review.googlesource.com/1640961 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640961" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/61/1640961/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I4a4b69efd5d6e9e5b183c7600a352888b57899d7" commit="d0fad947d7ae6e1e54b33ab4868527f0bc6661ea" commit_message="nebraska: Move AppData object to AppIndex AppIndex keeps the list of AppData objects internally. There is no point to keep AppData object globally available. Just move it to AppIndex instead. BUG=chromium:920404 TEST=unittest Change-Id: I4a4b69efd5d6e9e5b183c7600a352888b57899d7 Reviewed-on: https://chromium-review.googlesource.com/1640962 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640962" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/62/1640962/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ifdfc2314b723cafb69934f37ca078cc76d536355" commit="57e362ebc9309d2a670a04120e740e15a4a00a3a" commit_message="nebraska: Add a NebraskaProperties class These four parameters are almost used and passed everywhere: - install payload address - update payload address - install metadata directory path - update metadata directory path Added an object containing these parameters to send it around insteading of passing all of them. Made a lot of code more simpler. BUG=chromium:920404 TEST=unittest Change-Id: Ifdfc2314b723cafb69934f37ca078cc76d536355 Reviewed-on: https://chromium-review.googlesource.com/1640963 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640963" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/63/1640963/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie16d8016334e2d16d19a19d946b304c2fae635f0" commit="bf7530615fb4a99b06fa0c57daa95cbdde9fc44c" commit_message="nebraska: Cleanup error handling a little bit. Add a more structured Exception classes for Nebraska so it can easier be used as a library in devserver and its error be handled more gracefully. BUG=chromium:920404 TEST=unittest TEST=ran nebraska.py and sent some invalid requests. Change-Id: Ie16d8016334e2d16d19a19d946b304c2fae635f0 Reviewed-on: https://chromium-review.googlesource.com/1640964 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640964" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/64/1640964/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2ba14ab92fc9b822d1581b4633b6d88069b6d2f5" commit="943b1a3a869bead167acc116c502ab4d126c19a8" commit_message="nebraska: Convert " to ' Per our style guide we should use single quote for everything except when a string contains a single quote itself. This patch touches all the code to cleanup this problem as much as possible. BUG=chromium:920404 TEST=unittest TEST=nebraska.py Change-Id: I2ba14ab92fc9b822d1581b4633b6d88069b6d2f5 Reviewed-on: https://chromium-review.googlesource.com/1640965 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640965" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/65/1640965/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2a44aaeb498b6c02205fbdf70e161bf4565e1053" commit="9170af1b4a5a96d870bbdbc87cb2aa143537d93b" commit_message="nebraska: Allow examining the request Devserver will need to examin an incoming request for some values like board, version, etc in order to reply with correct payload. Restructure the Request and Response code a little bit to allow for that. Basically separate the request parsing logic from response and allow a request be parsed individually and the result be queried later. BUG=chromium:920404 TEST=unittest TEST=nebraska.py Change-Id: I2a44aaeb498b6c02205fbdf70e161bf4565e1053 Reviewed-on: https://chromium-review.googlesource.com/1640966 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640966" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/66/1640966/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iae56b89abe7e1d6c70da1b49b6ca1b54fbeb51f5" commit="c6ae40dd8b3c6eae339f4cc21bf976ca7fe39fe4" commit_message="nebraska: Check more error conditions on the request There are a few attributes that are kind of mandatory on at least on app tag in the list of request apps. Make sure they exist and there are not different values for them in different apps of the same request. Also restructure some unittests a little bit with default values so the code is cleaner and more readable. BUG=chromium:920404 TEST=unittest TEST=nebraska.py Change-Id: Iae56b89abe7e1d6c70da1b49b6ca1b54fbeb51f5 Reviewed-on: https://chromium-review.googlesource.com/1640967 Tested-by: Amin Hassani <ahassani@chromium.org> Commit-Ready: Amin Hassani <ahassani@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicolas Norvez <norvez@chromium.org> " fail_count="0" gerrit_number="1640967" owner_email="ahassani@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/67/1640967/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.19" change_id="Ia0a2f744359fac51816d33c4b47f66df8be6c557" commit="369ecee3b1d6e2a15860730459f13fcb242bf682" commit_message="Revert "CHROMIUM: wilco_ec: Add exclusive lock to event node" This reverts commit 88c16a3f5640ae0d40d493187e8b4e993af1e6f1. This is in preparation for re-committing a newer FROMLIST version of the patch that contains a few tweaks. BUG=b:133444996 TEST=See test in https://crrev.com/c/1628144 Cq-Depend: chromium:1628141, chromium:1628142, chromium:1628143, chromium:1628144 Signed-off-by: Nick Crews <ncrews@chromium.org> Change-Id: Ia0a2f744359fac51816d33c4b47f66df8be6c557 Reviewed-on: https://chromium-review.googlesource.com/1628140 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> " fail_count="0" gerrit_number="1628140" owner_email="ncrews@chromium.org" pass_count="0" patch_number="6" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/40/1628140/6" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.19" change_id="I734952046098e52e954d91aaca9a3f37bccec237" commit="3bb2138fa29b226748035325caeeffa77aa9a996" commit_message="Revert "FIXUP: CHROMIUM: wilco_ec: Add event handling" This reverts commit e65811cbe47329d6fd19fffed5372f0dbfa1db38. This is in preparation for re-committing a newer FROMLIST version of the patch that contains a few tweaks. BUG=b:133444996 TEST=See test in https://crrev.com/c/1628144 Cq-Depend: chromium:1628140, chromium:1628142, chromium:1628143, chromium:1628144 Change-Id: I734952046098e52e954d91aaca9a3f37bccec237 Signed-off-by: Nick Crews <ncrews@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1628141 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> " fail_count="0" gerrit_number="1628141" owner_email="ncrews@chromium.org" pass_count="0" patch_number="6" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/41/1628141/6" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.19" change_id="I94a75084d3f793e196e3e2961d039631d9ab2cd8" commit="f3646b52ab6333cc8677c47e974ccdaac84bfe3c" commit_message="Revert "FIXUP: CHROMIUM: wilco_ec: Add event handling" This reverts commit 3d182e0c5e52500fdea8b0c21dab091d9ec42a17. This is in preparation for re-committing a newer FROMLIST version of the patch that contains a few tweaks. BUG=b:133444996 TEST=See test in https://crrev.com/c/1628144 Cq-Depend: chromium:1628140, chromium:1628141, chromium:1628143, chromium:1628144 Change-Id: I94a75084d3f793e196e3e2961d039631d9ab2cd8 Signed-off-by: Nick Crews <ncrews@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1628142 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> " fail_count="0" gerrit_number="1628142" owner_email="ncrews@chromium.org" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/42/1628142/5" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.19" change_id="Ibd178b590ad554651f7f378b4e52548d80e8d719" commit="da43e206235392fe4d8cdf7dcb22b11bc89ca4db" commit_message="Revert "CHROMIUM: wilco_ec: Add event handling" This reverts commit 8d5efbab9fa2f71b3ea8e967bbda570b0a602d02. This is in preparation for re-committing a newer FROMLIST version of the patch that contains a few tweaks. BUG=b:133444996 TEST=See test in https://crrev.com/c/1628144 Cq-Depend: chromium:1628140, chromium:1628141, chromium:1628142, chromium:1628144 Change-Id: Ibd178b590ad554651f7f378b4e52548d80e8d719 Signed-off-by: Nick Crews <ncrews@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1628143 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> " fail_count="0" gerrit_number="1628143" owner_email="ncrews@chromium.org" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/43/1628143/5" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.19" change_id="I1d9feaa4d83f18011320bc8c35620504adf70f9d" commit="cf1c5c07d9ed0073258f39faf3952ad3c61480cc" commit_message="BACKPORT: FROMGIT: platform/chrome: wilco_ec: Add event handling The Wilco Embedded Controller can create custom events that are not handled as standard ACPI objects. These events can contain information about changes in EC controlled features, such as errors and events in the dock or display. For example, an event is triggered if the dock is plugged into a display incorrectly. These events are needed for telemetry and diagnostics reasons, and for possibly alerting the user. These events are triggered by the EC with an ACPI Notify(0x90), and then the BIOS reads the event buffer from EC RAM via an ACPI method. When the OS receives these events via ACPI, it passes them along to this driver. The events are put into a queue which can be read by a userspace daemon via a char device that implements read() and poll(). The event queue acts as a circular buffer of size 64, so if there are no userspace consumers the kernel will not run out of memory. The char device will appear at /dev/wilco_event{n}, where n is some small non-negative integer, starting from 0. Standard ACPI events such as the battery getting plugged/unplugged can also come through this path, but they are dealt with via other paths, and are ignored here. To test, you can tail the binary data with $ cat /dev/wilco_event0 | hexdump -ve '1/1 "%x\n"' and then create an event by plugging/unplugging the battery. Signed-off-by: Nick Crews <ncrews@chromium.org> (cherry picked from commit f7b0bc5eafa44941ddf92df6f46dd82cbfacec3e git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git chrome-platform-5.3) [ncrews: This CL updates the previous chromium version so it cleanly reflects the v4 version sent to the mailing list.] BUG=b:133444996 TEST=See the commit message for instructions. Only 64 events are available to read, even if I generate more than 64 of them. Cq-Depend: chromium:1628140, chromium:1628141, chromium:1628142, chromium:1628143 Change-Id: I1d9feaa4d83f18011320bc8c35620504adf70f9d Reviewed-on: https://chromium-review.googlesource.com/1628144 Tested-by: Nick Crews <ncrews@chromium.org> Commit-Ready: Nick Crews <ncrews@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Daniel Kurtz <djkurtz@chromium.org> " fail_count="0" gerrit_number="1628144" owner_email="ncrews@chromium.org" pass_count="0" patch_number="12" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/44/1628144/12" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I519e72e33a372763ef7d7073a2a615acdcb011fe" commit="28ed4ba145bb9d44dc37303cf22d54bc14dc77de" commit_message="drivers/ec: Return VBERROR_SUCCESS on successful TCPC FW update TCPC chips request EC Reboot to RO under 2 different situation: 1) to unlock the concerned remote_bus tunnel, if already in locked state 2) to get reset after the FW update is applied successfully. Returning the same error code in these different situation is ambiguos. Update the TCPC chips drivers to return VBERROR_SUCCESS on successful FW update, so that vboot can differentiate the situation and take appropriate action. BUG=b:128820536,b:119046668 BRANCH=None TEST=Boot to ChromeOS. Force a TCPC FW update and ensure that the EC reboots to RO after a successful TCPC update. Cq-Depend: chromium:1627302 Change-Id: I519e72e33a372763ef7d7073a2a615acdcb011fe Signed-off-by: Karthikeyan Ramasubramanian <kramasub@google.com> Reviewed-on: https://chromium-review.googlesource.com/1625866 Tested-by: Karthikeyan Ramasubramanian <kramasub@chromium.org> Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> " fail_count="1" gerrit_number="1625866" owner_email="kramasub@chromium.org" pass_count="0" patch_number="9" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/66/1625866/9" remote="cros" total_fail_count="6"/><pending_commit branch="master" change_id="Id3dd54ab1463a9db69cf3887a11d5f457311ff23" commit="d9e2ad8cd7841425cf70362195a8318003d326b3" commit_message="drivers/ec/vboot_aux_fw: Remove tunnel protect_status operation TCPC FW update is performed immediately after checking the need for FW update. Remote bus tunnel protection status is checked at both times and is redundant. Remove the redundant protect_status operation and invoke it directly just before applying the FW update. BUG=b:128820536,b:119046668 BRANCH=None TEST=Boot to ChromeOS. Change-Id: Id3dd54ab1463a9db69cf3887a11d5f457311ff23 Signed-off-by: Karthikeyan Ramasubramanian <kramasub@google.com> Reviewed-on: https://chromium-review.googlesource.com/1625867 Tested-by: Karthikeyan Ramasubramanian <kramasub@chromium.org> Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Jett Rink <jettrink@chromium.org> Reviewed-by: Furquan Shaikh <furquan@chromium.org> " fail_count="1" gerrit_number="1625867" owner_email="kramasub@chromium.org" pass_count="0" patch_number="9" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/67/1625867/9" remote="cros" total_fail_count="5"/><pending_commit branch="master" change_id="I72849620d90284e49cd1a9b31fc5eadede455c51" commit="bd8f6e2b790c387fe201def24a409d866dc72c00" commit_message="lib/ec_sync_all: Reboot EC to RO after successful AUX FW update Currently some chips that require AUX FW update request EC reboot to RO after the FW update is applied successfully while some chips do not. It is safe to request EC reboot to RO whenever AUX FW update is applied successfully so that all the chips that require AUX FW update gets reset to a clean state. Update tests to handle the updated code flow and return code correctly. BUG=b:128820536,b:119046668 BRANCH=None TEST=Ensure that the device boots to ChromeOS. Force a TCPC FW update and ensure that after it is successfully applied EC reboots to RO. Cq-Depend: chromium:1625866 Change-Id: I72849620d90284e49cd1a9b31fc5eadede455c51 Signed-off-by: Karthikeyan Ramasubramanian <kramasub@google.com> Reviewed-on: https://chromium-review.googlesource.com/1627302 Tested-by: Karthikeyan Ramasubramanian <kramasub@chromium.org> Commit-Ready: Karthikeyan Ramasubramanian <kramasub@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> " fail_count="0" gerrit_number="1627302" owner_email="kramasub@chromium.org" pass_count="0" patch_number="8" project="chromiumos/platform/vboot_reference" project_url="https://chromium-review.googlesource.com/chromiumos/platform/vboot_reference" ref="refs/changes/02/1627302/8" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="If423d5f0ea569dba0a74e6a86d47612b1dfa1487" commit="8d341f781887d34e83f58f943b163ddc0f574183" commit_message="drivers/i2c/cros_ec_tunnel: Add support to locate TCPC chip info Add a command to EC and an associated helper function to retrieve remote bus information for TCPC ports. BUG=b:128820536,b:119046668 BRANCH=None TEST=Boot to ChromeOS. Ensure that EC responds with I2C port information. 2019-05-23 11:30:43 [52.157015 HC 0x126] Cq-Depend: chromium:1614582 Change-Id: If423d5f0ea569dba0a74e6a86d47612b1dfa1487 Signed-off-by: Karthikeyan Ramasubramanian <kramasub@google.com> Reviewed-on: https://chromium-review.googlesource.com/1622589 Tested-by: Karthikeyan Ramasubramanian <kramasub@chromium.org> Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> " fail_count="1" gerrit_number="1622589" owner_email="kramasub@chromium.org" pass_count="0" patch_number="11" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/89/1622589/11" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.4" change_id="I2698cc3a7cec63d35133c8aa6301babdbb259c27" commit="f221f6eb7143e9a8a6e762f486f1fcb95a436f26" commit_message="FROMGIT: mwifiex: Fix possible buffer overflows at parsing bss descriptor mwifiex_update_bss_desc_with_ie() calls memcpy() unconditionally in a couple places without checking the destination size. Since the source is given from user-space, this may trigger a heap buffer overflow. Fix it by putting the length check before performing memcpy(). This fix addresses CVE-2019-3846. Reported-by: huangwen <huangwen@venustech.com.cn> Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 13ec7f10b87f5fc04c4ccbd491c94c7980236a74 git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master) BUG=chromium:972354 TEST=Wireless tests Change-Id: I2698cc3a7cec63d35133c8aa6301babdbb259c27 Signed-off-by: Guenter Roeck <groeck@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1656169 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Sean Paul <seanpaul@chromium.org> " fail_count="0" gerrit_number="1656169" owner_email="groeck@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/69/1656169/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.4" change_id="I62ed91ffeef2b553e8d1fade9aaaef8841d15468" commit="1a45261a13b2422e2c6e53d3f3dae3521d8835f9" commit_message="UPSTREAM: mwifiex: Fix skipped vendor specific IEs Mwifiex firmware inserts only Microsoft information element Allow other vendor specific IEs to pass from userspace Signed-off-by: Roman Stratiienko <roman.stratiienko@globallogic.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit bfc83ea196ad3e201eae7d156d1a95c403079b85) BUG=chromium:972354 TEST=Wireless tests Change-Id: I62ed91ffeef2b553e8d1fade9aaaef8841d15468 Signed-off-by: Guenter Roeck <groeck@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1656171 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Sean Paul <seanpaul@chromium.org> " fail_count="0" gerrit_number="1656171" owner_email="groeck@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/71/1656171/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.4" change_id="I71cf42c26901c15deb0178830745e45691c0aa3c" commit="0bd902f13070c9b6da5502427c98a0dba55afbc2" commit_message="FROMGIT: mwifiex: Fix heap overflow in mwifiex_uap_parse_tail_ies() A few places in mwifiex_uap_parse_tail_ies() perform memcpy() unconditionally, which may lead to either buffer overflow or read over boundary. This patch addresses the issues by checking the read size and the destination size at each place more properly. Along with the fixes, the patch cleans up the code slightly by introducing a temporary variable for the token size, and unifies the error path with the standard goto statement. Reported-by: huangwen <huangwen@venustech.com.cn> Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 69ae4f6aac1578575126319d3f55550e7e440449 git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master) BUG=chromium:972354 TEST=Wireless tests Change-Id: I71cf42c26901c15deb0178830745e45691c0aa3c Signed-off-by: Guenter Roeck <groeck@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1656172 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Sean Paul <seanpaul@chromium.org> " fail_count="0" gerrit_number="1656172" owner_email="groeck@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/72/1656172/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.19" change_id="Ia5faf50243e19c1755201212e04c8892d929785a" commit="f8548c614aea32648a4374b18c1f386118a95903" commit_message="CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus Emulate NMIs on systems where they are not available by using timer interrupts on other cpus. Each cpu will use its softlockup hrtimer to check that the next cpu is processing hrtimer interrupts by verifying that a counter is increasing. This patch is useful on systems where the hardlockup detector is not available due to a lack of NMIs, for example most ARM SoCs. Without this patch any cpu stuck with interrupts disabled can cause a hardware watchdog reset with no debugging information, but with this patch the kernel can detect the lockup and panic, which can result in useful debugging info. BUG=chromium:941638 TEST=see CL:I8eb9f2bd89a969c1f5ac94a63eb3033887dc4a5c Cq-Depend: chromium:1658514 Change-Id: Ia5faf50243e19c1755201212e04c8892d929785a Signed-off-by: Colin Cross <ccross@android.com> (mka@: ported from CrOS v4.4. Main delta is that upstream moved parts of watchdog.c to watchdog_hld.c, also we now have most new code in watchdog_other_cpu.c. A FROMLIST version with some comments can be found at https://patchwork.kernel.org/patch/1967551/ / https://lkml.kernel.org/r/1357941108-14138-1-git-send-email-ccross@android.com) Signed-off-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1643464 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="1" gerrit_number="1643464" owner_email="mka@chromium.org" pass_count="0" patch_number="7" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/64/1643464/7" remote="cros" total_fail_count="4"/><pending_commit branch="master" change_id="Ie3e1daa035c32b4afd710ba5237473ec0b3c3c03" commit="8b572ae9ebfe35ebfb83e53d5ae220b9486879fe" commit_message="lakitu: kernel: set CONFIG_HARDLOCKUP_DETECTOR_NMI=y lakitu selects CONFIG_HARDLOCKUP_DETECTOR. CL:1643464 introduced a new hardlockup detector and renamed the option to CONFIG_HARDLOCKUP_DETECTOR_NMI. There is still an option named CONFIG_HARDLOCKUP_DETECTOR, which is selected if any hardlockup detector is enabled. Add CONFIG_HARDLOCKUP_DETECTOR_NMI=y to the lakitu kernel config to keep things as they were before CL:1643464. BUG=chromium:941638 TEST=build lakitu kernel RELEASE_NOTE=None Cq-Depend: chromium:1643464 Change-Id: Ie3e1daa035c32b4afd710ba5237473ec0b3c3c03 Signed-off-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1658514 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Daniel Wang <wonderfly@google.com> " fail_count="1" gerrit_number="1658514" owner_email="mka@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/board-overlays" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays" ref="refs/changes/14/1658514/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.19" change_id="I8eb9f2bd89a969c1f5ac94a63eb3033887dc4a5c" commit="63dac9e8a242f26c06585cb88d053862ee1b5b30" commit_message="CHROMIUM: config: arm{32,64}: panic when a hardlockup is detected This is the result of running the following commands on a normalized configuration: echo CONFIG_BOOTPARAM_HARDLOCKUP_PANIC=y >> \ chromeos/config/armel/common.config echo CONFIG_BOOTPARAM_HARDLOCKUP_PANIC=y >> \ chromeos/config/arm64/common.config ./chromeos/scripts/kernelconfig olddefconfig BUG=chromium:941638 TEST=on veyron: echo userspace > /sys/class/devfreq/devfreq0/governor echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT => kernel panic after a few seconds ("Watchdog detected hard LOCKUP on cpu N") Change-Id: I8eb9f2bd89a969c1f5ac94a63eb3033887dc4a5c Signed-off-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1643465 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="1" gerrit_number="1643465" owner_email="mka@chromium.org" pass_count="0" patch_number="7" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/65/1643465/7" remote="cros" total_fail_count="4"/><pending_commit branch="master" change_id="I07368049361c9ffcf94dac54d2e0a703372b46e0" commit="61a56506d05eecdec6584fbf42fd83aed2606344" commit_message="shill: replace empty body {con,de}structors with `= default` An explicitly defaulted constructor/destructor is preferred over a user-defined empty body constructor/destructor as the former could potentially enable more opportunities in optimization. BUG=None TEST=Run unit test. Change-Id: I07368049361c9ffcf94dac54d2e0a703372b46e0 Reviewed-on: https://chromium-review.googlesource.com/1658413 Tested-by: Ben Chan <benchan@chromium.org> Commit-Ready: Ben Chan <benchan@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Alex Khouderchah <akhouderchah@chromium.org> " fail_count="0" gerrit_number="1658413" owner_email="benchan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/13/1658413/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I304cd74a76a1fa1443f660800522c93c2996935b" commit="bb38425af93296553ec1fbbc01093538c329b268" commit_message="shill: mark overridden methods with 'override' specifier BUG=None TEST=Run unit tests. Change-Id: I304cd74a76a1fa1443f660800522c93c2996935b Reviewed-on: https://chromium-review.googlesource.com/1658414 Tested-by: Ben Chan <benchan@chromium.org> Commit-Ready: Ben Chan <benchan@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Alex Khouderchah <akhouderchah@chromium.org> " fail_count="0" gerrit_number="1658414" owner_email="benchan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/14/1658414/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I0e60db79a9849409905f380483df53e279dcfd43" commit="c78fb5b1285e1498f2366e7fa3adb25dc9eff52e" commit_message="power: Refactor: correct TODO format. Derat recently deowned all the TODOs. In the process he changed TODO(derat) to TODO:. but the formatter complains whenever we make some changes to that file. So to calm the formatter, correct the format. BUG=None TEST=formatter does not complain. Change-Id: I0e60db79a9849409905f380483df53e279dcfd43 Reviewed-on: https://chromium-review.googlesource.com/1655285 Tested-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Commit-Ready: Ravi Chandra Sadineni <ravisadineni@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> " fail_count="0" gerrit_number="1655285" owner_email="ravisadineni@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/85/1655285/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8608509e2c8d053d545e25f3bcb298ca03256565" commit="8366726c6f6318088ae32fd88ec13f397719b65f" commit_message="power: Refactor: Make UpdateState() a little shorter. UpdateState is little big to follow. Move the logic that dictates the idle action out of UpdateState(). This should not make understanding dim,off, idle timeouts logic any harder. BUG=chromium:786721 TEST=unittests passes. Change-Id: I8608509e2c8d053d545e25f3bcb298ca03256565 Reviewed-on: https://chromium-review.googlesource.com/1651996 Tested-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Commit-Ready: Ravi Chandra Sadineni <ravisadineni@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Reviewed-by: Ben Chan <benchan@google.com> " fail_count="0" gerrit_number="1651996" owner_email="ravisadineni@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/96/1651996/4" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-3.18" change_id="Idaa729940d342f559fdeeb713bf808b07cc9c4cd" commit="e17b29dea5197497a97ff538e0cfbd5498d401d5" commit_message="BACKPORT: selinux: Generalize support for NNP/nosuid SELinux domain transitions In Chrome OS, NNP (NoNewPrivileges) is widely used to install seccomp rules in minijail, Chrome Browser, session manager, and etc. SELinux prevents domain transition of a process with NNP bit to transits to another domain, except bounded domains. Chrome OS will need to allow nnp_transition to make sure processed launched by minijail, session_manager, etc can end up at correct domains. Upstream messages: As systemd ramps up enabling NNP (NoNewPrivileges) for system services, it is increasingly breaking SELinux domain transitions for those services and their descendants. systemd enables NNP not only for services whose unit files explicitly specify NoNewPrivileges=yes but also for services whose unit files specify any of the following options in combination with running without CAP_SYS_ADMIN (e.g. specifying User= or a CapabilityBoundingSet= without CAP_SYS_ADMIN): SystemCallFilter=, SystemCallArchitectures=, RestrictAddressFamilies=, RestrictNamespaces=, PrivateDevices=, ProtectKernelTunables=, ProtectKernelModules=, MemoryDenyWriteExecute=, or RestrictRealtime= as per the systemd.exec(5) man page. The end result is bad for the security of both SELinux-disabled and SELinux-enabled systems. Packagers have to turn off these options in the unit files to preserve SELinux domain transitions. For users who choose to disable SELinux, this means that they miss out on at least having the systemd-supported protections. For users who keep SELinux enabled, they may still be missing out on some protections because it isn't necessarily guaranteed that the SELinux policy for that service provides the same protections in all cases. commit 7b0d0b40cd78 ("selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.") allowed bounded transitions under NNP in order to support limited usage for sandboxing programs. However, defining typebounds for all of the affected service domains is impractical to implement in policy, since typebounds requires us to ensure that each domain is allowed everything all of its descendant domains are allowed, and this has to be repeated for the entire chain of domain transitions. There is no way to clone all allow rules from descendants to their ancestors in policy currently, and doing so would be undesirable even if it were practical, as it requires leaking permissions to objects and operations into ancestor domains that could weaken their own security in order to allow them to the descendants (e.g. if a descendant requires execmem permission, then so do all of its ancestors; if a descendant requires execute permission to a file, then so do all of its ancestors; if a descendant requires read to a symbolic link or temporary file, then so do all of its ancestors...). SELinux domains are intentionally not hierarchical / bounded in this manner normally, and making them so would undermine their protections and least privilege. We have long had a similar tension with SELinux transitions and nosuid mounts, albeit not as severe. Users often have had to choose between retaining nosuid on a mount and allowing SELinux domain transitions on files within those mounts. This likewise leads to unfortunate tradeoffs in security. Decouple NNP/nosuid from SELinux transitions, so that we don't have to make a choice between them. Introduce a nnp_nosuid_transition policy capability that enables transitions under NNP/nosuid to be based on a permission (nnp_transition for NNP; nosuid_transition for nosuid) between the old and new contexts in addition to the current support for bounded transitions. Domain transitions can then be allowed in policy without requiring the parent to be a strict superset of all of its children. With this change, systemd unit files can be left unmodified from upstream. SELinux-disabled and SELinux-enabled users will benefit from retaining any of the systemd-provided protections. SELinux policy will only need to be adapted to enable the new policy capability and to allow the new permissions between domain pairs as appropriate. NB: Allowing nnp_transition between two contexts opens up the potential for the old context to subvert the new context by installing seccomp filters before the execve. Allowing nosuid_transition between two contexts opens up the potential for a context transition to occur on a file from an untrusted filesystem (e.g. removable media or remote filesystem). Use with care. Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov> Signed-off-by: Paul Moore <paul@paul-moore.com> (cherry picked from commit af63f4193f9fbbbac50fc766417d74735afd87ef) Signed-off-by: Qijiang Fan <fqj@chromium.org> BUG=chromium:963730 TEST=domain transition occurred for nnp processes Change-Id: Idaa729940d342f559fdeeb713bf808b07cc9c4cd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1577254 Reviewed-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Tested-by: Qijiang Fan <fqj@google.com> Commit-Queue: Qijiang Fan <fqj@google.com> (cherry picked from commit f6224cb5190b58a7b855f2b9e73dad8b58cda180) Reviewed-on: https://chromium-review.googlesource.com/1621726 Commit-Ready: Qijiang Fan <fqj@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Kenny Root <kroot@google.com> " fail_count="0" gerrit_number="1621726" owner_email="fqj@google.com" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/26/1621726/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iede906d62ef5c982a7cd682317c7d3eb52c8f469" commit="ec26e61bcdca55c7bc8ba57c316bf119af45cb12" commit_message="Reland "glibc: use __builtin_constant_p to skip trivial FORITFY checks" This is a reland of e2847859919eff7358e22e3c25e7059bfc24613a, which was reverted due to http://crbug.com/971440 . Now that the fix has landed (I3bc82e876c03a371820815ba4d0c64e8abee55ca), we can try to reland this. Original change's description: > glibc: use __builtin_constant_p to skip trivial FORITFY checks > > This is only done on functions which are presumed to be hot and > often-used, and which are trivially optimizeable by the compiler. > > The hope is that this might both make CrOS faster, and make the cost of > things like automatic initialization less: the compiler can't exactly > reason about arbitrary _chk functions, but it has a much easier time > reasoning about a regular memcpy, for example. > > BUG=None > TEST=Tryjobs > > Change-Id: Iae794f4e129abe262e7381b419202a490a9de9f7 > Reviewed-on: https://chromium-review.googlesource.com/1638320 > Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> > Tested-by: George Burgess <gbiv@chromium.org> > Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> > Reviewed-by: Manoj Gupta <manojgupta@chromium.org> BUG=chromium:971440 TEST=glmark2 passes with I3bc82e876c03a371820815ba4d0c64e8abee55ca applied Change-Id: Iede906d62ef5c982a7cd682317c7d3eb52c8f469 Reviewed-on: https://chromium-review.googlesource.com/1656730 Tested-by: George Burgess <gbiv@chromium.org> Commit-Ready: George Burgess <gbiv@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> " fail_count="0" gerrit_number="1656730" owner_email="gbiv@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/30/1656730/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3be5b6741f1e4f1922e6c0ba7d695c059e9d7cdd" commit="2482bdac699458e0b0e31b8d101b0fc995981c4e" commit_message="suite_scheduler.ini: Spread out load from Cts/Gts*Nightly suites Three CTS related nightly suites were generating a very high request load when scheduled together. On the coral shard, the load from these three suites comprises half of the daily requests. coral shard was unable to handle this load spike. This CL spreads out this load over a few hours, and moves it to night (PST timezone) to reduce impact. BUG=chromium:973935 TEST=unittests Change-Id: I3be5b6741f1e4f1922e6c0ba7d695c059e9d7cdd Reviewed-on: https://chromium-review.googlesource.com/1659332 Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Reviewed-by: Anh Le <anhdle@chromium.org> Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org> " fail_count="0" gerrit_number="1659332" owner_email="pprabhu@chromium.org" pass_count="0" patch_number="1" project="chromiumos/infra/suite_scheduler" project_url="https://chromium-review.googlesource.com/chromiumos/infra/suite_scheduler" ref="refs/changes/32/1659332/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I02c208880abfb0060cd07ffa905d2b9da0d0e159" commit="1386b24844c044c59fa1f18d2d3b6b474a70e769" commit_message="crash: improve crash_reporter_logs.conf docs BUG=None TEST=precq passes Change-Id: I02c208880abfb0060cd07ffa905d2b9da0d0e159 Reviewed-on: https://chromium-review.googlesource.com/1525128 Tested-by: Mike Frysinger <vapier@chromium.org> Commit-Ready: Mike Frysinger <vapier@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Ben Chan <benchan@google.com> " fail_count="0" gerrit_number="1525128" owner_email="vapier@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/28/1525128/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I316d37d3d0182c1d59824926d3aa41d785146608" commit="b5104607f86b327beae6cc05cd17f247dcf99b10" commit_message="permission_broker: allow Google USB serial devices Add CrOS debug board USB serial converter VID/PIDs to the IsDeviceAllowedSerial() check. BUG=chromium:956288 BUG=b:131336977 TEST=Attach Servo Micro to Linux VM; verify /dev/ttyUSB[012] nodes Change-Id: I316d37d3d0182c1d59824926d3aa41d785146608 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1641753 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicholas Verne <nverne@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Nick Sanders <nsanders@chromium.org> " fail_count="0" gerrit_number="1641753" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/53/1641753/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5c55a7313d51464a354d7d632bd5d3efd609dc3a" commit="37ccd3d900093e2f1e79712fd611f0efb11b991a" commit_message="libusb: rework accessing USB devices via file descriptor This CL reworks file descriptor handling on favor of libusb_wrap_sys_device() api introduced in upstream libusb past 1.0.22 release and builds on it by wiring up the new USBFS_CONNINFO_EX API that allows querying device's bus number, speed, and port path. We still have libusb_init_jailed(), libusb_open_fd(), and libusb_get_device_from_fd(), but they will be removed once crosvm stops using them. BUG=b:133773289 TEST=Build and deploy, try attaching a USB device to Crostini VM Change-Id: I5c55a7313d51464a354d7d632bd5d3efd609dc3a Reviewed-on: https://chromium-review.googlesource.com/1649266 Tested-by: Dmitry Torokhov <dtor@chromium.org> Commit-Ready: Dmitry Torokhov <dtor@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> " fail_count="0" gerrit_number="1649266" owner_email="dtor@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/66/1649266/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I638daea08f1ae478cb17ef6ab25a49eea75a7a8f" commit="4f175d4891bec01dd242be684303722078361d7b" commit_message="shill: consolidate MockControl and NiceMockControl MockControl and NiceMockControl differ only in those Create*Adaptor() methods where the latter returns a NiceMock version of those *AdapterInterface. Argubly, the NiceMockControl behavior is typically what we want. To simplify the code, this CL consolidates MockControl and NiceMockControl by keeping only MockControl with the NiceMockControl behavior. BUG=None TEST=Run unit tests. Change-Id: I638daea08f1ae478cb17ef6ab25a49eea75a7a8f Reviewed-on: https://chromium-review.googlesource.com/1654337 Tested-by: Ben Chan <benchan@chromium.org> Commit-Ready: Ben Chan <benchan@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Ben Chan <benchan@google.com> " fail_count="0" gerrit_number="1654337" owner_email="benchan@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/37/1654337/3" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="Id63b2d77bcca99f178f4f574390a4d1b8d958e10" commit="8de4c24e60952493df9e8453b5f912014f1f10f6" commit_message="BACKPORT: FROMLIST: tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations TPM 2.0 Shutdown involve sending TPM2_Shutdown to TPM chip and disabling future TPM operations. TPM 1.2 behavior was different, future TPM operations weren't disabled, causing rare issues. This patch ensures that future TPM operations are disabled. Signed-off-by: Vadim Sukhomlinov <sukhomlinov@google.com> [dianders: resolved merge conflicts with mainline] Signed-off-by: Douglas Anderson <dianders@chromium.org> (am from https://lore.kernel.org/patchwork/patch/1086755/) (also found at https://lkml.kernel.org/r/20190610220118.5530-1-dianders@chromium.org) Conflicts: drivers/char/tpm/tpm-chip.c ...upstream has commit a3fbfae82b4c ("tpm: take TPM chip power gating out of tpm_transmit()") and commit 719b7d81f204 ("tpm: introduce tpm_chip_start() and tpm_chip_stop()") and it didn't seem like a good idea to backport 17 patches to avoid the conflict. ;-) BUG=chromium:819268 TEST=mostly probabilistic due to shutdown behavior echo devices>/sys/power/pm_test cat /sys/class/tpm/tpm0/owned & cat /sys/class/tpm/tpm0/owned & echo mem>/sys/power/state & cat /sys/class/tpm/tpm0/owned & cat /sys/class/tpm/tpm0/owned & should return error once in a while Change-Id: Id63b2d77bcca99f178f4f574390a4d1b8d958e10 Signed-off-by: Douglas Anderson <dianders@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1495114 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Andrey Pronin <apronin@chromium.org> (cherry picked from commit 4465bd5a47080e477eecf4d2979c5c73280b5a5b) Reviewed-on: https://chromium-review.googlesource.com/1657342 Tested-by: Ross Zwisler <zwisler@chromium.org> Reviewed-by: Ross Zwisler <zwisler@chromium.org> " fail_count="0" gerrit_number="1657342" owner_email="dianders@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/42/1657342/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ia7390ed3e378d8bbe49118524b974373362f8182" commit="0cfe0479c044a5a91d34da2c37ba96bb4b56788e" commit_message="efitools: upgraded package to upstream Upgraded app-crypt/efitools to version 1.9.2 on amd64 BUG=chromium:967083 TEST=sudo emerge efitools Change-Id: Ia7390ed3e378d8bbe49118524b974373362f8182 Reviewed-on: https://chromium-review.googlesource.com/1650381 Tested-by: Daniel Kurtz <djkurtz@chromium.org> Commit-Ready: Daniel Kurtz <djkurtz@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Daniel Kurtz <djkurtz@chromium.org> " fail_count="0" gerrit_number="1650381" owner_email="mathewk@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/portage-stable" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/portage-stable" ref="refs/changes/81/1650381/2" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I4e6d7be1d635ab31a401c33630ae88e99c793638" commit="3fb2f78009531ad79551cf6697de489897646032" commit_message="gatt: add a user data field to API for primary service traversal This adds a user data field to gattClientUtilFindAndTraversePrimaryService() and gattCliUtilSvcTraversedCbk() and changes the references to them. BUG=b:134425062 TEST=build and run test program Change-Id: I4e6d7be1d635ab31a401c33630ae88e99c793638 Reviewed-on: https://chromium-review.googlesource.com/1656314 Tested-by: Miao-chen Chou <mcchou@chromium.org> Commit-Ready: Miao-chen Chou <mcchou@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Sonny Sasaka <sonnysasaka@chromium.org> " fail_count="0" gerrit_number="1656314" owner_email="mcchou@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/newblue" project_url="https://chromium-review.googlesource.com/chromiumos/platform/newblue" ref="refs/changes/14/1656314/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I00664555d98004f3af86ac1ae71acbb49b721c58" commit="ed5316d982e07fe6d18208527b2bf4986e144ab0" commit_message="shill: connection: Use per-device tables for all connections This change causes Connection to use a per-device table for all connections, and sets up routing rules such that the routing behavior complies with Shill's priority rules. In particular, VPNs must be used when applicable, and priorities of physical interfaces should follow Shill's Service sorting order. This implementation, as with the previous routing setup, does not adequately handle the case where two distinct interfaces have the same subnet. Future changes that allow for socket marking and routing based on packet marks will be needed to resolve this issue. Note that there is an existing issue (crbug.com/938629) where a non-default physical interface is used for all v4 or v6 traffic when the default physical interface does not have connectivity for that IP version. This CL does not change the existing behavior with respect to that issue. BUG=chromium:941597 TEST=-All unit tests are passing. -Manually verified routing tables/rules. -Manually ensured that new Chrome connections use the expected (i.e. highest priority) interface. -Manually verified with `ip route get` and `ip -6 route get` that source address selection uses the highest priority interface for both v4 and v6 when we have multiple connected interfaces. -OpenVPN through Android works as expected. -Play store is still able to search and download apps (i.e. can access the network). -`sudo apt install emacs` using Crostini succeeds. -`test_that ${DUT} network_WiFi_Perf.ht40` succeeds. -`test_that ${DUT} network_VPNConnect.l2tpipsec_psk` succeeds. Change-Id: I00664555d98004f3af86ac1ae71acbb49b721c58 Reviewed-on: https://chromium-review.googlesource.com/1590183 Tested-by: Alex Khouderchah <akhouderchah@chromium.org> Commit-Ready: Alex Khouderchah <akhouderchah@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Alex Khouderchah <akhouderchah@chromium.org> " fail_count="0" gerrit_number="1590183" owner_email="akhouderchah@chromium.org" pass_count="0" patch_number="11" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/83/1590183/11" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Ie2ac1db5dab122df35554e6d9fa990eb5893d3ab" commit="b1f7d457ed9bb56f4dbf60932f2b488410d4f23b" commit_message="CHROMIUM: go2001: enable driver We have forward-ported the go2001 driver from chromeos-3.14, now enable it in the intel-pineview config. BUG=b:134056823 TEST=builds Change-Id: Ie2ac1db5dab122df35554e6d9fa990eb5893d3ab Signed-off-by: Fletcher Woodruff <fletcherw@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1648329 Commit-Ready: Ross Zwisler <zwisler@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Ross Zwisler <zwisler@chromium.org> " fail_count="0" gerrit_number="1648329" owner_email="fletcherw@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/29/1648329/3" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.10" change_id="I59d2ffdc11c21b49fd08e8714a0265419c693884" commit="8200e04de37092ebddf364d6bdcf6df30da03e32" commit_message="CHROMIUM: fix up logic bug in chromiumos LSM This LSM does multiple security checks when userspace calls setuid, setreuid or setresuid. Make sure not to return early if one of the checks passes, since the others could still fail. Without doing this, userspace can trivially bypass the CAP_SETUID hardening logic. BUG=chromium:845640 TEST=security_ProcessManagementPolicy Signed-off-by: Micah Morton <mortonm@chromium.org> Change-Id: I59d2ffdc11c21b49fd08e8714a0265419c693884 Reviewed-on: https://chromium-review.googlesource.com/1566031 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dmitry Torokhov <dtor@chromium.org> " fail_count="0" gerrit_number="1566031" owner_email="mortonm@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/31/1566031/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ibab3731f48d5faad4177126445f5802d9b2ac6b6" commit="a4775a084f573cf696db7010069d25ec62e5fe82" commit_message="BACKPORT: FROMLIST: USB: add usbfs ioctl to retrieve the connection parameters Recently usfbs gained availability to retrieve device speed, but there is sill no way to determine the bus number or list of ports the device is connected to when using usbfs. While this information can be obtained from sysfs, not all environments allow sysfs access. In a jailed environment a program might be simply given an opened file descriptor to usbfs device, and it is really important that all data can be gathered from said file descriptor. This patch introduces a new ioctl, USBDEVFS_CONNINFO_EX, which return extended connection information for the device, including the bus number, address, port list and speed. The API allows kernel to extend amount of data returned by the ioctl and userspace has an option of adjusting the amount of data it is willing to consume. A new capability, USBDEVFS_CAP_CONNINFO_EX, is introduced to help userspace in determining whether the kernel supports this new ioctl. Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> BUG=b:133773289 TEST=Build and boot (am from https://patchwork.kernel.org/patch/10985613/) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ibab3731f48d5faad4177126445f5802d9b2ac6b6 Reviewed-on: https://chromium-review.googlesource.com/1651156 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Sean Paul <seanpaul@chromium.org> Reviewed-by: Guenter Roeck <groeck@chromium.org> (cherry picked from commit 8306c20ddc92d3550b192e9e5938aac259706753 and adjusted for minor context changes) Reviewed-on: https://chromium-review.googlesource.com/1657130 " fail_count="0" gerrit_number="1657130" owner_email="dtor@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/30/1657130/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I669fbd9b5c82bd8815463ad86d00eca61b73a829" commit="9fc70166e34fe10f19b91f52a36696ae49b4c42e" commit_message="smbprovider: Setup daemon-store directory. BUG=chromium:891462 TEST=Deploy and verify directory is created with correct permissions Change-Id: I669fbd9b5c82bd8815463ad86d00eca61b73a829 Reviewed-on: https://chromium-review.googlesource.com/1655189 Tested-by: Anand Mistry <amistry@chromium.org> Commit-Ready: Anand Mistry <amistry@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Sam McNally <sammc@chromium.org> " fail_count="0" gerrit_number="1655189" owner_email="amistry@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/89/1655189/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8d38162d61e2887fa44f48bb66ae815797b7fdda" commit="c893d6824f8824ae30f7b0e63ae16aa0c9f1e57a" commit_message="sarien: in UCM, fix 'Speaker' and 'Headphone' enable/disable sequence Because 'Speaker Playback Switch' and 'Headphone Playback Switch' are always set to opposite values in 'Speaker' and 'Headphone' enable/disable sequences, this means both playback switches are never off at the same time which should happen in the case of HDMI audio. Instead, only set respective playback switch values for each device separately. BUG=b:135048582 TEST='emerge-sarien chromeos-config-bsp-sarien chromeos-config chromeos-bsp-sarien' and deploy to DUT and check HiFi.conf Change-Id: I8d38162d61e2887fa44f48bb66ae815797b7fdda Signed-off-by: Joyce Toh <joyce.toh@intel.com> Reviewed-on: https://chromium-review.googlesource.com/1653737 Tested-by: Jairaj Arava <jairaj.arava@intel.corp-partner.google.com> Tested-by: Joyce Toh <joyce.toh@intel.corp-partner.google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Jairaj Arava <jairaj.arava@intel.corp-partner.google.com> Reviewed-by: Simon Glass <sjg@chromium.org> " fail_count="0" gerrit_number="1653737" owner_email="joyce.toh@intel.com" pass_count="0" patch_number="1" project="chromiumos/overlays/board-overlays" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays" ref="refs/changes/37/1653737/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I59d2ffdc11c21b49fd08e8714a0265419c693884" commit="9ca0d3a3664ddf0dad80a1eda6065a9f554566b2" commit_message="CHROMIUM: fix up logic bug in chromiumos LSM This LSM does multiple security checks when userspace calls setuid, setreuid or setresuid. Make sure not to return early if one of the checks passes, since the others could still fail. Without doing this, userspace can trivially bypass the CAP_SETUID hardening logic. BUG=chromium:845640 TEST=security_ProcessManagementPolicy Signed-off-by: Micah Morton <mortonm@chromium.org> Change-Id: I59d2ffdc11c21b49fd08e8714a0265419c693884 Reviewed-on: https://chromium-review.googlesource.com/1566070 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dmitry Torokhov <dtor@chromium.org> " fail_count="0" gerrit_number="1566070" owner_email="mortonm@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/70/1566070/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.4" change_id="I59d2ffdc11c21b49fd08e8714a0265419c693884" commit="1b3d26fba5d21d71f641df7cb4167750c25f2e53" commit_message="CHROMIUM: fix up logic bug in chromiumos LSM This LSM does multiple security checks when userspace calls setuid, setreuid or setresuid. Make sure not to return early if one of the checks passes, since the others could still fail. Without doing this, userspace can trivially bypass the CAP_SETUID hardening logic. BUG=chromium:845640 TEST=security_ProcessManagementPolicy Signed-off-by: Micah Morton <mortonm@chromium.org> Change-Id: I59d2ffdc11c21b49fd08e8714a0265419c693884 Reviewed-on: https://chromium-review.googlesource.com/1566071 Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dmitry Torokhov <dtor@chromium.org> " fail_count="0" gerrit_number="1566071" owner_email="mortonm@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/71/1566071/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2af0bb9fdc7330427105cce5c1a783525b4dce78" commit="44e91b2beee3e95636c34b7a0b16593d33cb15d2" commit_message="power: Make max dark suspend delay configurable This change makes the maximum time to wait for all suspend delays in dark resume to be configurable via a power constant. BUG=chromium:924762 TEST=Unit tests. Change-Id: I2af0bb9fdc7330427105cce5c1a783525b4dce78 Reviewed-on: https://chromium-review.googlesource.com/1643088 Tested-by: Abhishek Bhardwaj <abhishekbh@chromium.org> Commit-Ready: Abhishek Bhardwaj <abhishekbh@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> " fail_count="2" gerrit_number="1643088" owner_email="abhishekbh@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/88/1643088/4" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Id24e1ace912aeb226fbdc3647db2c595f6978d56" commit="4dd3353bb63ac1b1db69233e78c2c89906cceeea" commit_message="hatch: Add support for Helios and Kindred BUG=b:134773957, b:134775107 TEST=build mosys Change-Id: Id24e1ace912aeb226fbdc3647db2c595f6978d56 Reviewed-on: https://chromium-review.googlesource.com/1648791 Tested-by: Philip Chen <philipchen@chromium.org> Commit-Ready: Philip Chen <philipchen@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> " fail_count="0" gerrit_number="1648791" owner_email="philipchen@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/mosys" project_url="https://chromium-review.googlesource.com/chromiumos/platform/mosys" ref="refs/changes/91/1648791/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2a1a9b3c83fcd040830dbf99bc5702c8c3a2a892" commit="0b6b8cff48833d6efc1dd86fa8ff77e81a98b707" commit_message="shill: Consistently use angle brackets for #including libchrome headers BUG=None TEST=All unit tests are passing. Change-Id: I2a1a9b3c83fcd040830dbf99bc5702c8c3a2a892 Reviewed-on: https://chromium-review.googlesource.com/1658973 Tested-by: Alex Khouderchah <akhouderchah@chromium.org> Commit-Ready: Alex Khouderchah <akhouderchah@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Ben Chan <benchan@google.com> " fail_count="0" gerrit_number="1658973" owner_email="akhouderchah@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/73/1658973/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8d46dfea348689b58214771835faf098ed500845" commit="600c20ecb26636b07c90a64bb9cf271dc580686f" commit_message="coreboot: Support USB DBC USE flag This change will enable "CONFIG_SOC_INTEL_DEBUG_CONSENT=y" when USE=intel-dbc. This is uesed for USB DBC purpose. BUG=b:130203864 TEST=compile ok and USB DBC can be enabled if USE=intel-dbc Change-Id: I8d46dfea348689b58214771835faf098ed500845 Signed-off-by: Kane Chen <kane.chen@intel.com> Reviewed-on: https://chromium-review.googlesource.com/1564322 Commit-Ready: YH Lin <yueherngl@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Furquan Shaikh <furquan@chromium.org> " fail_count="1" gerrit_number="1564322" owner_email="kane.chen@intel.com" pass_count="0" patch_number="7" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/22/1564322/7" remote="cros" total_fail_count="1"/><lkgm version="12271.0.0-rc1"/></manifest> |
