linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Firmware class breaks udev
Date: Wed, 16 Mar 2005 07:27:38 +0000	[thread overview]
Message-ID: <4237DFEA.3080504@suse.de> (raw)
In-Reply-To: <42369BE6.7020807@suse.de>

Greg KH wrote:
> On Tue, Mar 15, 2005 at 02:09:17PM +0100, Hannes Reinecke wrote:
[ .. ]
>>The main problem is that firmware downloading does not fit in well with
>>the established functionalities:
>>
>>- modprobe returns after the device is fully initialised.
>>  -> firmware has to be loaded during modprobe, ie events have to
>>     be handled during modprobe
> 
> That can be changed, modprobe can return before the device is
> initialized.  I can change the driver to do this, if you wish.
> 
Oh, that would be good.
We should fix the firmware_class / any firmware-dependend device to
return (ie finish their probing) when the firmware device has been
registered in sysfs.
Then we have a chance to handle the firmware event, and on succesful
downloading the proper device will appear in sysfs. Something like
- handling pci event
  -> modprobe <corresponding module>
     -> generates firmware event
     -> returns
  -> event handling done
- handling firmware event
  -> download firmware
  -> device initialisation
     -> device_register()
        -> generate class device event
- handling class device event

>>- hotplug events are sent when the device registers itself with sysfs
>>  -> devices with firmware will then not be fully initialised
>>  -> the current hotplug subsystem does not distinguish between
>>     states 'device detected' and 'device initialised',
>>     so you can't model the firmware behaviour directly onto
>>     the linux hotplug subsystem.
> 
> Kay has a patch for that, which I will add to the tree in a few hours.
> 
> So, with your udev patch, is there still an immediate problem that needs
> to be fixed?
> 
Well, in principle.
I'd still prefer a proper solution as outlined above.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux AG				S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opÌk
_______________________________________________
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

  parent reply	other threads:[~2005-03-16  7:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15  8:25 Firmware class breaks udev Hannes Reinecke
2005-03-15 12:17 ` Kay Sievers
2005-03-15 13:09 ` Hannes Reinecke
2005-03-15 15:06 ` Kay Sievers
2005-03-15 15:20 ` Jon Smirl
2005-03-15 16:07 ` Hannes Reinecke
2005-03-15 16:20 ` Greg KH
2005-03-16  7:27 ` Hannes Reinecke [this message]
2005-03-16 15:52 ` Jon Smirl
2005-03-16 20:25 ` Kay Sievers
2005-03-17  6:01 ` Greg KH
2005-03-17  6:03 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4237DFEA.3080504@suse.de \
    --to=hare@suse.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).