On Mon, Jan 02, 2012 at 11:31:55PM +0000, Jack Stone wrote:
Rather than merging the drivers we could make the uvcvideo (or any other
generic driver) driver expose a "subdriver" interface that allows
another module to bind to the specific ID and add extra handling to
certain events. We could then use that interface to provide a firmware
driver for each device that needs it. The firmware driver could bind to
the bootstrap device and to the uvcvideo subdriver interface and it
would then have all the lifetime info we need. [Credit to Linus for
suggesting this idea]
No, the uvcvideo driver would need to call out to load the firmware
loader driver, otherwise you'll never know to load the firmware loader
driver.
--
Matthew Garrett | mjg59@srcf.ucam.org