From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753542Ab2ACAXR (ORCPT ); Mon, 2 Jan 2012 19:23:17 -0500 Received: from out5.smtp.messagingengine.com ([66.111.4.29]:55716 "EHLO out5.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753477Ab2ACAXO (ORCPT ); Mon, 2 Jan 2012 19:23:14 -0500 X-Sasl-enc: +XnnFSe5DZZJCaUCG+urZgkJMcRHjKeAYskoiY1kdhQH 1325550193 References: <20120102211904.GA15316@srcf.ucam.org> <20120102215028.GA15701@srcf.ucam.org> <20120102221235.GA16012@srcf.ucam.org> <20120102222920.GA16160@srcf.ucam.org> <20120102230037.GA16458@srcf.ucam.org> <4F023E6B.2020307@fastmail.fm> <20120103001356.GA17183@srcf.ucam.org> User-Agent: K-9 Mail for Android In-Reply-To: <20120103001356.GA17183@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: loading firmware while usermodehelper disabled. From: Jack Stone Date: Tue, 03 Jan 2012 00:22:58 +0000 To: Matthew Garrett CC: Linus Torvalds , Alan Stern , Oliver Neukum , Dave Jones , Linux Kernel , Larry Finger , Chaoming Li , "John W. Linville" , Greg Kroah-Hartman , USB list , Linux Wireless List Message-ID: <8e95c7e3-e9d5-43c4-8e6a-b8d40584cbd6@email.android.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Matthew Garrett wrote: >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. So we have a table of USB ids that list the devices that need firmware drivers. When the uvcvideo driver registers the firmware interface with a USB id that matches the list we load the firmware driver and pass it a "warm start" event so it can cache the firmware. As long as we can identify the devices that *might* need firmware then we are ok. Thanks, Jack -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.