On Sat, May 28, 2005 at 05:06:16PM +0200, Martin Husemann wrote:
> 
> What I would do is:
> 
>  - create two kernel functions fwdownload_register_hook and 
>    fwdownload_remove_hook. Drivers register their download function
>    with this - passing the device name and a token (most cases: softc pointer)
>  - create a /dev/fwdownload and a driver that only understands a very simple
>    ioctl (much like the isdn stuff)

How will one, after opening /dev/fwdownload, indicate _which_ device the
firmware one is handing the kernel is for?

Why not an ioctl on the actual device's node in /dev instead?  This might
require adding nodes in /dev for some controllers, but so what?