Google Git
Sign in
fuchsia/integration/705e2d76d826a78298a4cc00311de64ce9e029a7
commit
705e2d76d826a78298a4cc00311de64ce9e029a7
[log]
author
Clayton Wilkinson <wilkinsonclay@fuchsia.infra.roller.google.com>
Fri Sep 06 02:39:23 2024 +0000
committer
Copybara-Service <copybara-worker@google.com>
Thu Sep 05 19:41:52 2024 -0700
tree
ee5aa49dffb7ef181eb820081d3b79656d3b216c
parent
b550159a94f1d3cd99e42310dd9c4a76ffe9fed9 [diff]
[roll] Roll fuchsia Reland "[ffx][emu] Fixing OVMF support for arm64"

The SDK roll process in google3 is updated. I am planning to run LSC before re-merging.

> Reason for revert: Emulator fails to start in google3 (b/362784552)
>

This changes how the file name of the VARS file
is handled when configuring the emulator for EFI support.

 The x64 and arm64 implementations have different names, previously,
it was assumed they were the same.

Original-Bug: b/356870849
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1110474
Original-Revision: 19536dee69577f30647758f4a1d132cff802a337
GitOrigin-RevId: f55a3a29d8c559d9415483214df6325cef187f62
Change-Id: Ibe0b010fb01d5f77f6c62a43494708b6afd30ef5
1 file changed
tree: ee5aa49dffb7ef181eb820081d3b79656d3b216c
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.