[display][fidl] SetLayerImage: illegalize signal fence

Make it illegal to provide a valid event ID for `signal_event_id`.
Add a new method `SetLayerImage2` which removes the `signal_event_id`
argument, but otherwise behaves identically.  Clients should migrate
to `SetLayerImage2`, then `SetLayerImage` can be deleted.

Fixed: 370994314
Change-Id: I7d17adea793b4738a86ba8dbe46348f0abb57a36
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1140317
Commit-Queue: Victor Costan <costan@google.com>
Fuchsia-Auto-Submit: Josh Gargus <jjosh@google.com>
Fuchsia-Auto-Submit: Victor Costan <costan@google.com>
Reviewed-by: Yilong Li <liyl@google.com>
API-Review: Victor Costan <costan@google.com>
4 files changed
tree: 28df72950dd593026a13ce95d0ff296db9b7a14e
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. infra/
  7. products/
  8. scripts/
  9. sdk/
  10. src/
  11. third_party/
  12. tools/
  13. zircon/
  14. .clang-format
  15. .clang-tidy
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .ignore
  23. analysis_options.yaml
  24. AUTHORS
  25. BUILD.gn
  26. CODE_OF_CONDUCT.md
  27. CONTRIBUTING.md
  28. fuchsia.code-workspace
  29. LICENSE
  30. OWNERS
  31. PATENTS
  32. pyproject.toml
  33. pyrightconfig.json
  34. README.md
  35. rustfmt.toml
  36. shac.star
  37. shac.textproto
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.