From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Asynchronous driver initialization and request_firmware/post
Date: Fri, 11 Mar 2005 19:07:26 +0000 [thread overview]
Message-ID: <9e473391050311110719d1e49b@mail.gmail.com> (raw)
BenH and I have been emailing about how to load a driver that needs
firmware or posting. He wants to do this asynchronously to support
things like suspend/resume. It looks like the current synchronous
request_firmware() is going to have trouble with resume.
Is there a mechanism for letting the driver load and probe with the
probe function doing nothing but triggering the firmware/posting event
and then mark the driver off-line somehow? The problem is, you load
the driver and the firmware or post program is mission or set up
wrong, how do you inform the user of the error? Shouldn't this be done
in a standard way?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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=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
next reply other threads:[~2005-03-11 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 19:07 Jon Smirl [this message]
2005-03-11 19:38 ` Asynchronous driver initialization and request_firmware/post Jon Smirl
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=9e473391050311110719d1e49b@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.