Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

PSA: Drivers that expose Inspect will now find it under driver manager

17 views
Skip to first unread message

Clayton McCray

unread,
Aug 5, 2024, 4:06:58 PM8/5/24
to drive...@fuchsia.dev, Anantha Keesara
If you don't read the Inspect of drivers, you can disregard this email

Hi driver folks,

As part of making the Inspect of drivers more efficient, it will now always show up under bootstrap/driver_manager.

You can now use name-filter-lists to refer to specific drivers under driver manager.

For example, if you previously used `ffx inspect show --manifest sdmmc.cm`, you would now use `ffx inspect show "bootstrap/driver_manager:[name=aml-sd-emmc]root"`. (Note that you will often need to quote a selector using brackets or wildcards when working on the command line)

The name filter list syntax is documented here.

Some DFv2 driver specific docs can be found here.

If you don't know the name that you should use with a driver, the selector `bootstrap/driver_manager:[...]root` will match all trees exported under driver manager.

Thanks and sorry for any workflow disruptions,
Clayton

Yifei Teng

unread,
Aug 5, 2024, 4:18:52 PM8/5/24
to drivers-dev, Clayton McCray, Anantha Keesara
Just to confirm, would the inspect published by driver components get _moved_ from under driver components to under driver_manager, or would they get _duplicated_ such that you can access them in both locations?

Clayton McCray

unread,
Aug 5, 2024, 4:30:48 PM8/5/24
to Yifei Teng, drivers-dev, Anantha Keesara
Moved. The inefficiency was that it was previously duplicated in most cases.

Clayton McCray

unread,
Aug 29, 2024, 5:36:28 PM8/29/24
to Yifei Teng, drivers-dev, Anantha Keesara
This change is being partially reverted after further discussion with surajmalhotra@. You will once again find a driver's Inspect under its own moniker.

Apologies for the churn around your `ffx inspect` invocations. I think this is the final change for the foreseeable future to where driver Inspect is located.

Note that name filter lists as originally described still exist. So, if you need to write a selector for a component, you can get around the instability of driver monikers by combining a name filter with wildcards, like the following:

 ```
ffx inspect show "bootstrap/*-drivers*:[name=display-coordinator]root
```

But again, I know many of you previously used invocations such as `ffx inspect show --manifest display-coordinator.cm`, and that will once again work.

The CL implementing this: fxr/1110082 
Reply all
Reply to author
Forward
0 new messages