Re: Rework of request firmware

[Greg KH <greg@kroah.com>]

On Mon, Mar 21, 2005 at 03:37:00AM +0100, Kay Sievers wrote:
> On Sun, 2005-03-20 at 15:39 -0500, Jon Smirl wrote:
> > On Sun, 20 Mar 2005 21:25:17 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > > Could you please define the requirements for that subsystem _first_ and
> > > make sure that everything we currently know of is covered before adding
> > > stuff to the core. I'm pretty sure that this will have to change several
> > > times before we get that right.
> > 
> > The base device support is missing two things I need:
> > 1) some mechanism to run the POST program
> 
> I've put that on the list below.
> 
> > 2) subdirectories under class_device for hotplug monitors
> 
> Childs of class devices is somewhere on Greg's list, I think. :)
> Don't know how close we are to allow that. Greg?

Closer than we were last week, now that I have a lot of the class rework
done :)

thanks,

greg k-h
> Questions:
> =====
>  o How do we reprobe a device if we can't unload the module?

Kick it from userspace.  See pci for an example of how to do this.

>  o From which DEVPATH should the requests originate from?
>    The module itself in sysfs, the physical device, the class
>    device? Or stick with with our own temporary class device
>    for the requests?

I think the "physical device" or whatever it is represented by in the
sysfs device tree.

>  o Do we need any timeout? If yes, how is that to be handled?

Yes.  Don't know.

>  o Will all users/probers be able to schedule its work
>    until the request comes back from userspace? 

They had better :)

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_idh82&alloc_id\x15148&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel