Google Git
Sign in
chromium / chromiumos / third_party / coreboot / refs/heads/firmware-volteer-13672.B
commita03071a268b0bd5a841d6f153647767e53d7e70f[log] [tgz]
authorNick Vaccaro <nvaccaro@google.com>Wed Jan 24 16:14:31 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 24 17:39:36 2024
treef425a42f74afa9b8a2fa7419c31e150b6a686338
parent46f61eba8156aa3e10bb8d93414b5dbedc9bdb9e [diff]
Revert^2 "UPSTREAM: mb/google/volteer/eldrid: Fix touchscreen under Windows"

This reverts commit 46f61eba8156aa3e10bb8d93414b5dbedc9bdb9e.

Reason for revert: This change should not have merged to chromium as it will break linux implementation.

Original change's description:
> Revert "UPSTREAM: mb/google/volteer/eldrid: Fix touchscreen under Windows"
>
> This reverts commit c4060b2199207be158e9911a143ba38cff18f2c1.
>
> Reason for revert: Increasing reset time makes resume time failed. This change will not be reverted downstream to keep touchscreen works on Linux and Win11.
>
> BUG=b:319372039
> TEST=power_UiResume test pass.
>
> Original change's description:
> > UPSTREAM: mb/google/volteer/eldrid: Fix touchscreen under Windows
> >
> > Under Win11, a longer delay after asserting reset is needed for the
> > Goodix touchscreen to init properly. Increase the reset delay to match
> > that used for the Goodix touchscreen by other volteer variants (120ms).
> >
> > TEST=build/boot Win11, Linux on eldrid variant with Goodix touchscreen,
> > verify functional.
> >
> > (cherry picked from commit b575397c7fb349d69854d6cca26154cf2f0477c5)
> >
> > Original-Change-Id: I489f037f0bbade9567aad2ad64404a5ac66965d9
> > Original-Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
> > Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/72580
> > Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
> > Original-Reviewed-by: Angel Pons <th3fanbus@gmail.com>
> > GitOrigin-RevId: b575397c7fb349d69854d6cca26154cf2f0477c5
> > Change-Id: Id63793d29fe2a5e9482b0b23c85bc61322384253
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/4243140
> > Tested-by: Nick Vaccaro <nvaccaro@google.com>
> > Auto-Submit: Nick Vaccaro <nvaccaro@google.com>
> > Reviewed-by: Zhuohao Lee <zhuohao@chromium.org>
> > Commit-Queue: Nick Vaccaro <nvaccaro@google.com>
>
> Change-Id: I20c0bb90baf91ba0384875c332f78ae962859a86
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/5196337
> Commit-Queue: Casper Chang <casper_chang@wistron.corp-partner.google.com>
> Reviewed-by: Subrata Banik <subratabanik@chromium.org>
> Tested-by: Casper Chang <casper_chang@wistron.corp-partner.google.com>

BUG=b:319372039

Change-Id: I75a1f5d8a3781c2b76827572133bfa8805a05e45
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/5234588
Tested-by: Nick Vaccaro <nvaccaro@google.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Nick Vaccaro <nvaccaro@google.com>
Commit-Queue: Nick Vaccaro <nvaccaro@google.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
1 file changed
tree: f425a42f74afa9b8a2fa7419c31e150b6a686338
  1. configs/
  2. Documentation/
  3. LICENSES/
  4. payloads/
  5. spd/
  6. src/
  7. tests/
  8. util/
  9. .checkpatch.conf
  10. .clang-format
  11. .editorconfig
  12. .gitignore
  13. .gitmodules
  14. .gitreview
  15. AUTHORS
  16. COPYING
  17. gnat.adc
  18. MAINTAINERS
  19. Makefile
  20. Makefile.inc
  21. PRESUBMIT.cfg
  22. README.md
  23. toolchain.inc
README.md

coreboot README

coreboot is a Free Software project aimed at replacing the proprietary BIOS (firmware) found in most computers. coreboot performs a little bit of hardware initialization and then executes additional boot logic, called a payload.

With the separation of hardware initialization and later boot logic, coreboot can scale from specialized applications that run directly firmware, run operating systems in flash, load custom bootloaders, or implement firmware standards, like PC BIOS services or UEFI. This allows for systems to only include the features necessary in the target application, reducing the amount of code and flash space required.

coreboot was formerly known as LinuxBIOS.

Payloads

After the basic initialization of the hardware has been performed, any desired “payload” can be started by coreboot.

See https://www.coreboot.org/Payloads for a list of supported payloads.

Supported Hardware

coreboot supports a wide range of chipsets, devices, and mainboards.

For details please consult:

Build Requirements

  • make
  • gcc / g++ Because Linux distribution compilers tend to use lots of patches. coreboot does lots of “unusual” things in its build system, some of which break due to those patches, sometimes by gcc aborting, sometimes - and that‘s worse - by generating broken object code. Two options: use our toolchain (eg. make crosstools-i386) or enable the ANY_TOOLCHAIN Kconfig option if you’re feeling lucky (no support in this case).
  • iasl (for targets with ACPI support)
  • pkg-config
  • libssl-dev (openssl)

Optional:

  • doxygen (for generating/viewing documentation)
  • gdb (for better debugging facilities on some targets)
  • ncurses (for make menuconfig and make nconfig)
  • flex and bison (for regenerating parsers)

Building coreboot

Please consult https://www.coreboot.org/Build_HOWTO for details.

Testing coreboot Without Modifying Your Hardware

If you want to test coreboot without any risks before you really decide to use it on your hardware, you can use the QEMU system emulator to run coreboot virtually in QEMU.

Please see https://www.coreboot.org/QEMU for details.

Website and Mailing List

Further details on the project, a FAQ, many HOWTOs, news, development guidelines and more can be found on the coreboot website:

https://www.coreboot.org

You can contact us directly on the coreboot mailing list:

https://www.coreboot.org/Mailinglist

Copyright and License

The copyright on coreboot is owned by quite a large number of individual developers and companies. Please check the individual source files for details.

coreboot is licensed under the terms of the GNU General Public License (GPL). Some files are licensed under the “GPL (version 2, or any later version)”, and some files are licensed under the “GPL, version 2”. For some parts, which were derived from other projects, other (GPL-compatible) licenses may apply. Please check the individual source files for details.

This makes the resulting coreboot images licensed under the GPL, version 2.