Re: Driver index

15 views
Skip to first unread message

Benjamin Prosnitz

unread,
Feb 4, 2021, 12:46:30 PM2/4/21
to Geevarghese V K, fidl-dev, drive...@fuchsia.dev

On Thu, Feb 4, 2021, 12:39 PM Geevarghese V K <jince...@gmail.com> wrote:
Dear team,

I have seen a new module "driver-index" got introduced. What is the purpose of this?

--
All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
---
To unsubscribe from this group and stop receiving emails from it, send an email to fidl-dev+u...@fuchsia.dev.

Suraj Malhotra

unread,
Feb 4, 2021, 1:47:09 PM2/4/21
to Benjamin Prosnitz, Geevarghese V K, fidl-dev, drive...@fuchsia.dev
Hi Geevarghese,

The driver index is a new component which will perform the role of enumerating available drivers and performing bind program evaluation to decide what drivers should bind to spawned devices - currently these operations are performed by the driver manager. This is part of an ongoing re architecture to make driver manager into a component runner for drivers, and splitting out duties which don't make sense for a runner to implement.

Cheers,
Suraj

Suraj Malhotra

unread,
Feb 4, 2021, 3:06:51 PM2/4/21
to Geevarghese V K, drive...@fuchsia.dev
Yes, that is the plan.

On Thu, Feb 4, 2021 at 12:05 PM Geevarghese V K <jince...@gmail.com> wrote:
So in future, will individual drivers become a component?

Geevarghese V K

unread,
Feb 4, 2021, 3:10:54 PM2/4/21
to Suraj Malhotra, drive...@fuchsia.dev
Great, thanks!
Reply all
Reply to author
Forward
0 new messages