This allows PkgUri and RepoUri to be used as keys in HashMaps and
HashSets.

Change-Id: I30f7fb1a893ec84ce83bb2bff6c9ede4fd39bf1a

The new Provider interface replaces both openat and the get_handle
ioctl. The new approach to getting a controller client is to:
1. Open the device-controller device. This no longer creates a new
instance.
2. Call one of the new Provider methods on the service handle to the
device.
3. Maintain the connection by keeping alive two channels: one for the
device instance, and one for the FIDL interface.

Eventually those two channels should be merged, but that's blocked on
support for llcpp, see ZX-3889.

ZX-2826 #done
ZX-3277 #comment removes open_at from the display driver

Tests:
Boot device (tests virtcon)
display_test
gfxtest (tests framebuffer library)
vkcube_on_fb (tests vulkan swapchain library)
scenic app (tests DisplayWatcher)
recovery app (tests rust framebuffer library)
gfxlatency

Can't run:
display_capture_test (no HW)

Change-Id: Ie187e43692ed7c947920511188c98da38c9843f3

Don't call 1.1 apis if not supported.

Change-Id: I41ae1803f3b05ce110106646dcefba81e5c20926

The 'waterfall' demo is based on the soon-to-be-deleted
"PaperRenderer 1".  Delete it, and rename 'waterfall2' to
'waterfall'.

ES-193 #done

Change-Id: I19d8508754ed6f072340cc6a6bee2d5e928d3adc

This cl adds, ViewRef struct which will be used for Semantic
Registration process by the client.

Testing:
  * Build
  * Manually installed on device.

MI4-1736 #comment

Change-Id: I96defec65cc8f9f536490e56f844fd234fb3fbbd

When we handle the zbi_cpu_config_t type on ARM systems we will now
convert it to a new flat topology and feed it into the topology
subsystem. This allows us to have the Topology subsystem as the source
of truth for topology logic on all platforms. Eventually we will remove
the zbi_cpu_config_t alltogether.

ZX-3068
Test: Booted and "k ut all" on:
*Qemu arm
*Astro
*Vim2

Change-Id: Ia22eb29146b56e030d540dd92e469e48f0726e4b

This also remove the MessageLoopTarget as an interface and makes what
previous was MessageLoopAsync that. This means that now there is no
abstract interface for the target but rather a concrete implementation.

TC-447 # Removed from debug agent.

TEST=Manual: Running binaries and components.
     Unit & Integration tests (fx run-test debug_agent_tests)

Change-Id: Ia2b41ca660cebae70d8d35e1348c97cbddffab68

These are no longer valid build arguments. Please use
base_package_labels, cache_package_labels, and universe_package_labels
instead.

Change-Id: I3213b7d72b84b35c75d21106af91e648b415ca09

Change-Id: I543310f31119e8639e918a978ef940af3ea90f03

Change-Id: I94162ee8c71c057ed90b5f7a53e98c545cc309be

WLAN-1050 #done

Test: fx full-build
Change-Id: I083db44fadaad0d8e77179103b4ab47ae65d9e70

Change-Id: Id9c2406b7fb715b5bbb91ab999be687692569e29

This is intended as a transitional step on replacing abigen with banjo.
The goal of this backend is for it to be a relatively short-lived as a
migration path:

1. Create abigen backend for banjo
2. Replace hand-written abigen with output of equivalent .banjo file as
   a Zircon build step
3. Create additional backend(s) that generate the current outputs of
   abigen, but as there are currently 13, proceed one or a handful at a
   time
4. Once the build is consuming files generated directly from
   banjo, remove the abigen backend (and the abigen tool).

ZX-3882 #comment [abigen][banjo] Add beginnings of abigen backend for banjo

Test: new tests added in tools/banjo/banjo/test/abigen

Change-Id: I96a332e96c6d6332cfe74b62fbffd852f8a9e9b7

CLion has an incomplete index w/o these additions.

Test: Verified index is now complete.
Change-Id: Ifd3638e9197af515c3396a4373034c0eb9bea6af

Change-Id: I631566d0d9c5ecc96f7d45238fe5c094b4ef2842

The old gen/build_arguments.md files from the pre-fuchsia.git repos
have not been updated in a long time.  The docs-roller bot now
updates //docs/gen/build_arguments.md instead.  But since that file
didn't exist, bot runs have not been updating *any* file for the
Fuchsia GN build arguments documentation, only the new Zircon file.

Remove the defunct peridot/ file and move the garnet/ file to
//docs where the next bot run should update it properly.

Change-Id: I6430b4af4ca796fa12ae366ce899c1c3afc0856b

Bug: DX-1201
Bug: DX-1269
Change-Id: I19936ae5489f485c745fff86c464c879c897cfb7

Change-Id: I8260bb84c136fa4f088c99934cacad575b8c4df3

This fixes the huge volume of bad readings seen due to unimplemented
wlan_rx_info for data frames. Subsequent work should resolve these instances
of missing info.

WLAN-1018

Test=ran existing unit tests and verified histogram fixed in `wlan stats`

Change-Id: I3395b65c4060664f20a3bdff0d08b03fbc8458cd

- actions: convertTrace() accepts multiple files

  - Pass additional zedmon file when -zedmon specified

- Temporary: Local copy of minimal tracing event structs required for
  zedmon trace

- Hardcoded zedmon pseudoprocess PID: "zedm" ASCII

- Channel-based zedmon interface

  - On run(): Stream CSV into structs, then JSON bytes

    - Return channels for data and errors

  - On stop(): Stop streaming and cleanup

Change-Id: Ibf3e9693714d310f62c99aec7f10474a571fc829

Change-Id: I7d190d7293ebb77184fd36bfed934c2c1cb27eda

Change-Id: I512517aa1d0f76a07a6c54dc504db8f4da1366e2

As part of migrating towards a unified A/B/R boot image configuration
for all supported boards the following changes were made:
* A chromebook board file was added.
** VBOOT images are only built for the new target.
** VBOOT images are treated similarly to how signed images on other
   boards are treated.
* The EFI image was deduplicated into bootloader.
* The KERNC image was deduplicated into ZIRCON-A.
* Support for a VB_META_R partition was added.
* zedboot version was updated (due to breaking changes)

ZX-3861

Tested: Paved pixelbook, NUC, astro, and vim2
Change-Id: I2344048ef69dd7b5e53004c707a261f5e0e0bb93

This removes some repetition in the items
`fuchsia_uri::FuchsiaBootUri` and `fuchsia_uri::FuchsiaPkgUri`.

Change-Id: I400a15b98a8fc6e476fa15c3d920c1d5a13780ab

Change-Id: Icd85ede1a0f4f9492e91907039ba012a908db456

Previously, since a waker was reused between loops in recv_all, a
deadlock was possible:

    TASK 1  -> poll_recv_event
            <- pending, will wake task 1 on next chan.recv_from msg
    TASK 2  -> send MyRequest, poll_recv_msg_response
            <- pending, will wake task 2 on next chan.recv_from msg
    **event comes in, chan.recv_from's waker is called**
	    <- wake task 2
    TASK 2  -> poll_recv_msg_response
            <- pending, will wake task 2 on next chan.recv_from msg
	    <- but hey also event is ready so wake task 1
    TASK 1  -> poll_recv_event
            <- ready, will wake task 1 on next chan.recv_from msg
    **task 1 calls await!(Timer(1 year))**
    **MyRequest reply comes in, chan.recv_from's waker is called**
            <- wake task 1
	       ^ this will not poll or get recv_all called, since task 1
	         is waiting on a timer, not a FIDL event, so TASK 2 will
		 never be woken up with its now-ready response.

Eventually, after one year, task 1 will stop awaiting and either drop
the EventReceiver or await!() on it again, either of which will call
recv_all and wake task 2. This may be a contrived example, but I ran
into it when Task 1 requested a (futures-aware) lock that task 2 was
holding. Task 1 was blocked waiting on the lock, and task 2 never got
woken because of the logic above.

This CL makes several changes:

- recv_all now uses the same logic as wake_any to pick a Waker, instead
of using the initially-used waker, which may not be polling if the
Future is Ready after recv_all. In the example above, the last
poll_recv_event would cause the still-waiting task 2 to be registered as
the recv_from msg waker, instead of the no-longer-waiting task 1.
- poll_recv_msg_response and poll_recv_event now update their waker
*before* calling recv_all, so that recv_all can correctly select their
waker to be the next chan.recv_from waker if they'll still be Pending
after recv_all is called.
- When the EventListener is woken, it is now set to
EventListener::WillPoll to match the Received behavior in responses.
This means the comment in wake_any() is not necessary, since
already-called events that are now awaiting on something else will not
be selected in get_pending_worker(). EventListener::New was also renamed
to EventListener::WillPoll to clarify this new use of the state. This
also means the previous comment in wake_any is no longer relevant, since
an event receiver will only be the waker if got Pending on its last
poll.

Change-Id: Id3e23fd4575d220117207e43b6a5ce6b1e419f33

Change-Id: Ic129292339bda65c5a59e98a72cca5e257e40953

This change adds skeleton for 2 protocol ops. One for requesting the
hardware voltage constraints of a regulator, the other for requesting
for a particular voltage.

Test: fx full-build. No functionality added here. Will do more tets when
functionality is added to these protocols.

Change-Id: I499ea4790eb86cb17ab216e9c64446e9b5df4ca3

This CL fixes a null dereference in mediaplayer that occurs when the
player cannot access a URL.

TEST: fx shell present_view \
  fuchsia-pkg://fuchsia.com/mediaplayer_test_util#meta/mediaplayer_test_util.cmx \
  http://ia800201.us.archive.org/12/items/BigBuckBunny_328/BigBuckBunny.ogv
Change-Id: Ib95a0f4c0dff81ec8ef05b6600d0abef03679b9c

Test: CQ

Change-Id: I992bebbb45c0b5f5316b32bd6eebe5762eb33c1c

Change-Id: Ide75beb0e1f6b35137a5103019ef0219dfbb27cc

This CL addresses some misunderstandings concerning constraints on
various DNS/mDNS-related string values (chiefly around max length)
and makes string checking more thorough. Also added unit tests.

TEST: fx run-test mdns_tests
Change-Id: I4ca0bbbab463378fb11381bbb01fb59b9f4779b6

Change-Id: Id63faf19219bdec97bc2c63e81e24b7f5e10d0cd

Change-Id: I2ea40a4ea46dedc08f429707ca79d1611de5f89f

This reverts commit 6be4d762.

Reason for revert: Looks like the build errors were unrelated to this commit.

Original change's description:
> Revert "[thinfs] fix nil pointer dereference."
> 
> This reverts commit 36b9d349.
> 
> Reason for revert: I received a LUCI email saying that this breaks asan builds.
> 
> Original change's description:
> > [thinfs] fix nil pointer dereference.
> > 
> > This CL fixes a nil pointer dereference that happens in the
> > thinfs/zircon/rpc package.
> > 
> > The issue is that the `directoryWrapper is not correctly initialized,
> > not setting the cookies map. Upon calls to GetToken(), the dictionary is
> > dereferenced and that causes a panic.
> > 
> > The commit just makes sure that the cookies map is initialized
> > correctly, and adds a test for it.
> > 
> > ZX-3928: Done
> > 
> > TEST=/pkfs/packages/go_thinfs_tests/0/test/go_thinfs_test
> > 
> > Change-Id: I4686714f547f8a759d11dcc2e9414ce60e37707d
> 
> TBR=kulakowski@google.com,smklein@google.com,mvanotti@google.com
> 
> Change-Id: I8bd13bf33f3ee744afed06d4e5d43e74b4349041
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true

TBR=kulakowski@google.com,smklein@google.com,mvanotti@google.com

Change-Id: I96f2afca116fac4a8f83dfbc15113234907cac17
No-Presubmit: true
No-Tree-Checks: true
No-Try: true

ZX-3581 #done

Change-Id: Id55af08c814ec2921e31dfd9f707281a0d6b830f

I additionally grepped the tree for instances of NetErr that weren't
StatusOk that left the Message field empty; this is the only one.

Change-Id: I607748dd6a91083e0f74decc16743be3879b8633

Bug: DX-1045 #done
Change-Id: I277dd292b4f35a5cf3953928fab0d6bd72770803

TEST=Manually ran and observed that warning in console went away.

Change-Id: I548e20d7df618d4cf031bff12237233a7f8bd493

Change-Id: Idf4fbd28106e45c982fee6f024e27f6d30469052