> For PCI drivers, you implement the ::suspend and ::remove hooks.
> > I have a race free version of pm_send_all if you want it.
> Is this the same thing that is in 2.4.3-pre3?
Mine is race free for the basics, his is a far far more elegant solution to the
whole problem space. It might be 2.5 stu
John Fremlin wrote:
> Why not set up the device driver to handle PM events itself. See
> Documentation/pm.txt under Driver Interface.
For PCI drivers, you implement the ::suspend and ::remove hooks.
> I have a race free version of pm_send_all if you want it.
Is this the same thing that is in 2.
Thomas Hood <[EMAIL PROTECTED]> writes:
> Sometimes modules need to be reloaded in order
> to cause some sort of reinitialization (of the
> driver or of the hardware) to occur.
Why not set up the device driver to handle PM events itself. See
Documentation/pm.txt under Driver Interface.
I have
On Tue, 6 Mar 2001 14:17:28 -0800 (PST),
Thomas Hood <[EMAIL PROTECTED]> wrote:
>My question is: Is there some better way of blocking
>all open() calls to a particular device driver while
>processes using it are being killed off?
Not yet. There have been some off list discussions about redoing
Hi. Here's my question, with a little introduction.
Sometimes modules need to be reloaded in order
to cause some sort of reinitialization (of the
driver or of the hardware) to occur.
Sometimes this has to be done every time a machine
is suspended. E.g., some sound driver modules
need to be relo
5 matches
Mail list logo
