On Sat, May 05, 2007 at 12:08:55PM +0200, Pavel Machek wrote:
> Hi!
>
> > > Here's a (compile tested only) patch that does this on a per-device
> > > basis, which is smaller, and should work just as well as your patch.
> > >
> > > It creates a new file in the power/ directory for every device
On Sat, May 05, 2007 at 12:08:55PM +0200, Pavel Machek wrote:
Hi!
Here's a (compile tested only) patch that does this on a per-device
basis, which is smaller, and should work just as well as your patch.
It creates a new file in the power/ directory for every device called
Hi!
> > Here's a (compile tested only) patch that does this on a per-device
> > basis, which is smaller, and should work just as well as your patch.
> >
> > It creates a new file in the power/ directory for every device called
> > "can_suspend". Write a '0' to it to prevent that device from
On Saturday, 5 May 2007 11:24, Ingo Molnar wrote:
>
> * Greg KH <[EMAIL PROTECTED]> wrote:
>
> > Here's a (compile tested only) patch that does this on a per-device
> > basis, which is smaller, and should work just as well as your patch.
> >
> > It creates a new file in the power/ directory
* Greg KH <[EMAIL PROTECTED]> wrote:
> Here's a (compile tested only) patch that does this on a per-device
> basis, which is smaller, and should work just as well as your patch.
>
> It creates a new file in the power/ directory for every device called
> "can_suspend". Write a '0' to it to
* Greg KH [EMAIL PROTECTED] wrote:
Here's a (compile tested only) patch that does this on a per-device
basis, which is smaller, and should work just as well as your patch.
It creates a new file in the power/ directory for every device called
can_suspend. Write a '0' to it to prevent
On Saturday, 5 May 2007 11:24, Ingo Molnar wrote:
* Greg KH [EMAIL PROTECTED] wrote:
Here's a (compile tested only) patch that does this on a per-device
basis, which is smaller, and should work just as well as your patch.
It creates a new file in the power/ directory for every
Hi!
Here's a (compile tested only) patch that does this on a per-device
basis, which is smaller, and should work just as well as your patch.
It creates a new file in the power/ directory for every device called
can_suspend. Write a '0' to it to prevent that device from being
Hi!
> > it might be better to do this centrally in sysfs, via a per-device
> > attribute, to individually enable suspend and resume on a per device
> > basis, but my sysfs-fu is not strong enough for that now ;-)
>
> Here's a (compile tested only) patch that does this on a per-device
> basis,
Hi!
it might be better to do this centrally in sysfs, via a per-device
attribute, to individually enable suspend and resume on a per device
basis, but my sysfs-fu is not strong enough for that now ;-)
Here's a (compile tested only) patch that does this on a per-device
basis, which is
On Thu, Jan 25, 2007 at 12:05:01PM +0100, Ingo Molnar wrote:
> Subject: [patch] suspend/resume debugging: device filter
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> this patch implements the /sys/power/filter attribute, which takes a
> string. If a device's name matches the f
Hi!
> Subject: [patch] suspend/resume debugging: device filter
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> this patch implements the /sys/power/filter attribute, which takes a
> string. If a device's name matches the filter string (exactly), then
> that device is excl
Hi.
On Thu, 2007-01-25 at 12:05 +0100, Ingo Molnar wrote:
> it might be better to do this centrally in sysfs, via a per-device
> attribute, to individually enable suspend and resume on a per device
> basis, but my sysfs-fu is not strong enough for that now ;-)
Yeah. I was thinking recently of
Subject: [patch] suspend/resume debugging: device filter
From: Ingo Molnar <[EMAIL PROTECTED]>
this patch implements the /sys/power/filter attribute, which takes a
string. If a device's name matches the filter string (exactly), then
that device is excluded from suspend/resume.
th
Subject: [patch] suspend/resume debugging: device filter
From: Ingo Molnar [EMAIL PROTECTED]
this patch implements the /sys/power/filter attribute, which takes a
string. If a device's name matches the filter string (exactly), then
that device is excluded from suspend/resume.
this can
Hi.
On Thu, 2007-01-25 at 12:05 +0100, Ingo Molnar wrote:
it might be better to do this centrally in sysfs, via a per-device
attribute, to individually enable suspend and resume on a per device
basis, but my sysfs-fu is not strong enough for that now ;-)
Yeah. I was thinking recently of
Hi!
Subject: [patch] suspend/resume debugging: device filter
From: Ingo Molnar [EMAIL PROTECTED]
this patch implements the /sys/power/filter attribute, which takes a
string. If a device's name matches the filter string (exactly), then
that device is excluded from suspend/resume
On Thu, Jan 25, 2007 at 12:05:01PM +0100, Ingo Molnar wrote:
Subject: [patch] suspend/resume debugging: device filter
From: Ingo Molnar [EMAIL PROTECTED]
this patch implements the /sys/power/filter attribute, which takes a
string. If a device's name matches the filter string (exactly
18 matches
Mail list logo
