mikus wrote:
> > > Please - make sure that it takes a multi-second duration of
> > > the power button to perform a *complete* shutdown.
> >
> > no, definitely not. training users to hold down power buttons
> > is/was a huge mistake, since getting in the habit is a little
> > like parking
> > Please - make sure that it takes a multi-second duration of
> > the power button to perform a *complete* shutdown.
>
> no, definitely not. training users to hold down power buttons
> is/was a huge mistake, since getting in the habit is a little
> like parking your car by letting it hit the
hi mikus --
mikus wrote:
> > what do you think? 'a' or 'b'?
>
> As long as the possibility exists to manually edit a configuration file,
> I myself will change the sleep behavior to be like 'before'.
yes, the new scheme ('b') is configurable.
>
> I do not care whether it takes a keystro
> what do you think? 'a' or 'b'?
As long as the possibility exists to manually edit a configuration file,
I myself will change the sleep behavior to be like 'before'.
I do not care whether it takes a keystroke, or pushing the CPU button,
to wake from 'sleeping' -- I'll learn through experience.
Hi,
> Why will the screen blank? Why not just deactivate the
> backlight? Is the DCON's power draw sufficiently high that
> blanking the screen represents real savings?
Yes, it's >100mw, AFAIK.
- Chris.
--
Chris Ball
One Laptop Per Child
___
On 03/23/10 15:16, Paul Fox wrote:
> are you comfortable having two
> laptop states:
> - dark screen wakeable from keyboard
> - dark screen _not_ wakeable from keyboard
> that are visually indistinguishable?
by the way, if you have entered "dark screen wakeable from key
Paul Fox wrote:
> now:
> in the new scheme, the idle sequence has changed: after a
> fairly brief period of inactivity, the system will suspend,
> leaving the screen on. (the user may not even know this has
> happened.) assuming there is still no keyboard activity, a
> little
isaac wrote:
> On 03/23/10 15:16, Paul Fox wrote:
> > are you comfortable having two
> > laptop states:
> > - dark screen wakeable from keyboard
> > - dark screen _not_ wakeable from keyboard
> > that are visually indistinguishable?
>
> by the way, if you have e
b.
--
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
> We could also consider just having the touchpad be available for
> wake-from-idle-sleep, and not the keyboard, since that way you wouldn't have
> any side effects from the wakeup key. But I think having the side effects
> isn't a big deal, so I'd go with your proposed (b).
I've gotten into th
Hi,
> further, if you choose 'a': are you comfortable having two
I think this is "if you choose 'b'".
> laptop states: - dark screen wakeable from keyboard - dark screen
> _not_ wakeable from keyboard that are visually indistinguishable?
> is it worth adding yet another LED blink
recent releases of XO-1.5 (and also of F11-on-XO1, if we can ever
get suspend/resume working properly again) have a new default
behavior with regard to idle suspend. i'm soliciting opinions on
how to fine-tune this new behavior.
before:
in the past on XO-1, the screen would dim, and after a
12 matches
Mail list logo
