Hi
We are trying to enhance the power management module in OLPC. We thought
of developing the application using Gtk+ in C.
We have tried one small program in OLPC. Built using gtk+ in C. It displays
the battery details of the OLPC. We have run the program in Linux platform
and got the
Hi guys,
Is there a way to disable automatic power management from terminal?
Thx!
Thomas
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
OLPC now uses the olpc-hardware-manager python service to do power
management tasks. This is not really suitable for long term use, and we
can't easily do clever things with this infrastructure.
I'm proposing to use OHM (ohm.freedesktop.org) to do the clever things,
and apply system w
Hi,
if you want to use an activity to display that information this thread
may help you:
http://lists.laptop.org/pipermail/devel/2008-March/012280.html
Simon
Aswathy wrote:
> Hi
>
> We are trying to enhance the power management module in OLPC. We thought
> of developing the
On 02.04.2008, at 09:54, Aswathy wrote:
>
> Hi
>
> We are trying to enhance the power management module in OLPC. We
> thought of developing the application using Gtk+ in C.
>
> We have tried one small program in OLPC. Built using gtk+ in C. It
> displays the battery
2008/4/2 Aswathy <[EMAIL PROTECTED]>:
>
> Hi
>
>We are trying to enhance the power management module in OLPC. We thought
> of developing the application using Gtk+ in C.
>
> We have tried one small program in OLPC. Built using gtk+ in C. It displays
> the batter
Hi,
Thanks for the suggestions... The whole scenario goes like this:
As part of our final year project, we have decided to do a power management
application for the OLPC.
As per our ideas, we have decided to implement the features that normal
laptops have as a power management
On Wed, Apr 2, 2008 at 12:54 PM, Aswathy <[EMAIL PROTECTED]> wrote:
> This is our whole idea. Do give suggestions on this. Also how we can make
> this application compatible with the OLPC. Actually we were really new to
> the OLPC. We just came to know about OLPC last year. We started thinking
> a
Hi,
> Is there a way to disable automatic power management from terminal?
touch /etc/powerd/flags/inhibit-suspend # permanent, until rm
or
touch /var/run/powerd-inhibit-suspend/1 # temporary, until next boot
- Chris.
--
Chris Ball
One Laptop Per Ch
Richard Hughes wrote:
> • When system idle for > 30 seconds we turn the screen off
Remember that we have a DCON that acts as a hardware frame buffer. The
screen turning off if you don't use the machine for 30s is a terrible
user experience and absolutely not an option -- but the screen freezing
af
On Fri, 2007-06-08 at 10:35 -0400, Kent Quirk wrote:
> Is there a mechanism for either applications or users to change the
> parameters? And what constitutes "idle"?
Very good question. In GNOME, idle is where the keyboard or mouse is not
moved, and the session is not inhibited.
> In particular,
but both
individuals and applications may want the ability to tweak them.
Kent
Richard Hughes wrote:
> I'm thinking about system power management interactions for the OLPC. Sofar
> I've got:
> • When system idle for > 10 seconds and on battery we dim screen to 40%• When
&g
On Fri, 2007-06-08 at 10:51 -0400, Ivan Krstić wrote:
> Richard Hughes wrote:
> > • When system idle for > 30 seconds we turn the screen off
>
> Remember that we have a DCON that acts as a hardware frame buffer. The
> screen turning off if you don't use the machine for 30s is a terrible
> user exp
On Fri, 2007-06-08 at 14:51 +0100, Richard Hughes wrote:
> OLPC now uses the olpc-hardware-manager python service to do power
> management tasks. This is not really suitable for long term use, and we
> can't easily do clever things with this infrastructure.
Right; we'd pretty m
On Fri, 2007-06-08 at 11:14 -0400, Dan Williams wrote:
> On Fri, 2007-06-08 at 14:51 +0100, Richard Hughes wrote:
> > OLPC now uses the olpc-hardware-manager python service to do power
> > management tasks. This is not really suitable for long term use, and we
> > can'
On Fri, 2007-06-08 at 11:29 -0400, Dan Williams wrote:
> > This is way too laid-back. We should be suspending and letting the DCON
> > refresh the display within a few seconds of going idle. A minute is
> > really a long time.
>
> let me clarify here; this is somewhat activity dependent. Ebook,
On Fri, 2007-06-08 at 11:42 -0400, Chris Ball wrote:
> Hi,
>
>> Is there a mechanism for either applications or users to change the
>> parameters? And what constitutes "idle"?
>
> A first shot at what constitues "idle" is if all of the below are true:
>
>* if the CPU isn't under load
On 08/06/07 16:49 +0100, Richard Hughes wrote:
> On Fri, 2007-06-08 at 11:42 -0400, Chris Ball wrote:
> > Hi,
> >
> >> Is there a mechanism for either applications or users to change the
> >> parameters? And what constitutes "idle"?
> >
> > A first shot at what constitues "idle" is if all
On Fri, 2007-06-08 at 11:14 -0400, Dan Williams wrote:
> On Fri, 2007-06-08 at 14:51 +0100, Richard Hughes wrote:
> > OLPC now uses the olpc-hardware-manager python service to do power
> > management tasks. This is not really suitable for long term use, and we
> > can'
Hi,
> Is there a mechanism for either applications or users to change the
> parameters? And what constitutes "idle"?
A first shot at what constitues "idle" is if all of the below are true:
* if the CPU isn't under load
* if the video on the screen isn't changing
* if we aren't dea
Richard Hughes wrote:
> On Fri, 2007-06-08 at 11:42 -0400, Chris Ball wrote:
>
...
>> This should be fine -- when your opponent's move's network traffic hits
>> the Marvell chip, it will assert a wakeup and the CPU'll come back and
>> process the traffic.
>>
>
> That's some pretty sweet har
On Fri, 2007-06-08 at 15:55 +0100, Richard Hughes wrote:
> On Fri, 2007-06-08 at 10:51 -0400, Ivan Krstić wrote:
> > Richard Hughes wrote:
> > > • When system idle for > 30 seconds we turn the screen off
> >
> > Remember that we have a DCON that acts as a hardware frame buffer. The
> > screen turn
On 08.06.2007 17:57, Jordan Crouse wrote:
> On 08/06/07 16:49 +0100, Richard Hughes wrote:
>> On Fri, 2007-06-08 at 11:42 -0400, Chris Ball wrote:
>>>* if there isn't a software tick (dynticks/tickless) planned for the
>>> very near future
>> Can we get this info from the kernel?
>
> Prob
Richard Hughes wrote:
> Surely you don't want to suspend during a system update or software
> installation... We can even use the HAL lock interface to do this.
If the machine idle heuristics think it's okay to suspend during system
update or software install, something's off.
That said, I'm tryi
> What's the power difference between freeze and off? If it's not
> substantial, I totally agree with you.
>From a B3 board running off wall power (12V)
No battery installed
Measuring current on the power cord:
Running Q2C11 firmware:
535 mA - idle loop, display lights on (no memory activity
Hi Richard,
On Fri, Jun 08, 2007 at 02:51:00PM +0100, Richard Hughes wrote:
> OLPC now uses the olpc-hardware-manager python service to do power
> management tasks. This is not really suitable for long term use, and we
> can't easily do clever things with this infrastructure.
>
Hello everyone, I'm trying to perform some tests on XO battery life
performance and I have some questions which I couldn't find a clear answer
in the wiki or this list:
- When the battery level is "critically low" the OS (Sugar 0.88 based
Dextrose) performs a safe shutdown. I would like to know wh
s are difficult to implement
quickly.
since my heart is with more quasi-embedded systems than the XO's
current incarnation, part of my goal was to do a rewrite which
was not dependent on hald, dbus, or X11 -- power management
should work well from a console screen, and be available even if
non
Hello
I am trying to figure out more about how power management work on the
OLPC. It's quite different from what I am used (acpi, etc) and the
documentation/scripts doesn't seem up to date
For example, I saw references to respeclaration in the xinitrc while
it's supposed t
ismael wrote:
> Hello everyone, I'm trying to perform some tests on XO battery life
> performance and I have some questions which I couldn't find a clear answer
> in the wiki or this list:
i'm sure richard will chime in, but here's a start.
>
> - When the battery level is "critically low" t
Thanks, for starters this is really useful, because it's not at all similar
to what I've been observed. The computer powers off with battery levels
between 10-15% and the led starts blinking around 5-10%. I'm using several
batteries on the same XO 1.0 computer. Granted, the batteries are not fresh
On 03/24/2011 08:55 AM, Ismael Schinca wrote:
> Thanks, for starters this is really useful, because it's not at all
> similar to what I've been observed. The computer powers off with battery
> levels between 10-15% and the led starts blinking around 5-10%. I'm
> using several batteries on the same
That's exactly what I wanted to know. How was the SOC evaluated when the
battery lost capacity. If there was some estimation on the battery loss or
just a full capacity assumption and then early poweroff.
I have several batteries, some of them pretty old (that's the idea). A
couple of S/Ns:
006020
On 03/24/2011 09:15 AM, Richard A. Smith wrote:
> Whats the serial number of your battery? You may also want to run a
> olpc-pwr-log run with that battery so you can determine what the actual
> capacity of the battery is.
Even better you are in a position to help me figure out how best to deal
w
On 03/24/2011 09:25 AM, Ismael Schinca wrote:
> I have several batteries, some of them pretty old (that's the idea). A
> couple of S/Ns:
>
> 00602 080616 110002384
> 00602 080608 11600
The mfg is embedded in the serial number pos 6-11 format YYMMDD
So these 2 batteries where produced 2008/0
We would really like to have a relatively accurate result *as fast as
possible *of the condition of a battery. That's what I'm trying to get to.
I could run the olpc-pwr-log on 15 batteries aprox. Used batteries but in a
"probably good" condition.
I'm also trying to get some really bad but function
OK. Just read this email.
So the plan would be:
- Start from a fully charged battery, run the olpc-pwr-log script until
poweroff.
- Remove battery, plug XO, run script and insert battery until fully
charged.
If you would prefer a different test please let me know.
Ismael
2011/3/24 Richard A. Smi
On 03/24/2011 09:53 AM, Ismael Schinca wrote:
> OK. Just read this email.
> So the plan would be:
> - Start from a fully charged battery, run the olpc-pwr-log script until
> poweroff.
> - Remove battery, plug XO, run script and insert battery until fully
> charged.
Yes. Or the other way around if
On 03/24/2011 09:53 AM, Ismael Schinca wrote:
>
> If you would prefer a different test please let me know.
oh and if this is a build that running powerd then you need to stop it
or disable power management and turn off dpms screen blanking. On 1.5
dpms is not active but it is on XO 1.0
On 03/24/2011 09:45 AM, Ismael Schinca wrote:
> We would really like to have a relatively accurate result *as fast as
> possible *of the condition of a battery. That's what I'm trying to get to.
> I could run the olpc-pwr-log on 15 batteries aprox. Used batteries but
> in a "probably good" conditio
On 03/24/2011 10:31 AM, Richard A. Smith wrote:
> If you run _exactly_ the same test under the same conditions. Same
> temperature, same test duration, same XO, then it might be possible to
> compare the current voltage,
Battery temperature will also be a concern. If you test the discharge
immed
e for us humans
than batteries ;) )
The closer I might get, which I think could be pretty close is:
- Install the SAME fresh OS image and firmware version on all the test XOs
- Disable power management in every XO
- Keep the XOs close together
- The laptops batteries are mostly charged, so it wi
ME fresh OS image and firmware version on all the test XOs
- Disable power management in every XO.
and dpms. xset -dpms from the sugar terminal other wise the screen will
turn off in 20 minutes and change the power draw.
- The laptops batteries are mostly charged, so it will be a charge after
dis
office should be within reason. I just
> don't want the profiles generated in an office and then the test run in a
> outside warehouse at 33C. Or the curves generated on a XO-1 with build 8.2
> but the test run on a 1.5 with build 10.1.3. That sort of thing.
>
> The closer I
just
> > don't want the profiles generated in an office and then the test run in a
> > outside warehouse at 33C. Or the curves generated on a XO-1 with build 8.2
> > but the test run on a 1.5 with build 10.1.3. That sort of thing.
> >
> > The closer I migh
;> > >>
>> > >
>> > > Yes. Sorry my use of the word exactly was probably too strong. I
>> don't
>> > > mean that it has to be 25 degC ambient and only that temperature.
>> The temp
>> > > fluctuations in a air
t and use a very short test window.
>>> ie 20
>>> > > minutes or so.
>>> > >
>>> > >
>>> > > - The air conditioning in our building is quite frankly chaotic so
>>> > >> temperature is really variable (which i
On 03/31/2011 03:43 PM, Ismael Schinca wrote:
Richard, Ceibal about to start working heavily in reworking how to
classify used batteries. Due to the number of batteries involved, we
were asked to devise a "good enough" procedure to estimate the battery
condition in less than 10 minutes. The plan
Thanks! This is very useful information. I'll try to run some new tests and
try to look at the data more thoroughly. The new batteries' capacity is
pretty puzzling. I'll repeat the tests on these batteries and add a couple
more of new ones to get more results.
I think it's a good idea to think abou
On 04/05/2011 09:33 AM, Ismael Schinca wrote:
> Thanks! This is very useful information. I'll try to run some new tests
> and try to look at the data more thoroughly. The new batteries' capacity
> is pretty puzzling. I'll repeat the tests on these batteries and add a
> couple more of new ones to ge
On 04/19/2011 03:52 PM, Pablo Iguiniz wrote:
> Hello Richard,
>
> This is Eng. Javier Iguiniz from Ceibal. Ismael has recently changed
> work so I am now taking over part of his tasks, in particular the
> testing related to the XO batteries.
Welcome Javier.
> I tried to catch up with the plan, so
e range
0.3V to 1.9V. So you'd need some appropriate additional peripherals
(voltage divider?) to measure the voltage in the range that you are
mentioning (around 12V)
>
> How could we get the power management interface? Is it the terminal itself?
>
> To consume low power for each
Hi All,
I would like to do some power management testing on my G1G1 unit.
I heard that there is now a way to completely power down the radio
from the GUI or the command line without restarting the machine. Is
this correct?
I have 703 on my machine but that OS version seems nothing special in
mathematical diversion. Perhaps
one day, after we have achieved our intended aggressive power management,
it will be time to implement this algorithm.
Comment on the Talk page, if you feel so inclined.
- --Ben
P.S. Thanks to isforinsects and hhardy for enabling math on the wiki.
-BEGIN PGP SIGNATURE
Chris Ball wrote:
> We made an incremental step in 8.2, offering automatic power management
> that is disabled by default, and I propose a talk covering what needs
> to happen for us to be comfortable taking the next step to enable it
> by default in 9.1.
+1. I'm going to expan
Hi,
This e-mail describes the work plan for power management during December.
I've filed bugs for each item, so this plan is the list of bugs that
should be fixed during December.
Bugs I plan to fix:
* #2765 -- Need to turn off DCON after some time in idle suspend
* #3732 -- ARP broad
> configurable timeouts for screen dim and sleep. the dim
> level is configurable.
My XO systems are plugged in to the AC, so I normally leave them
running 24/7. But in the middle of the night if I happen to walk
by, I notice if they are acting as "light sources". Two concerns
(for which I d
ile the backlight is still lit. It would be useful if
> rawhide supported dimming/shutting_off the screen when no one is
> looking at it (irrespective of whether the CPU is doing work or not).
i'm sure rawhide will gain a power management solution of some
sort. probably ohmd will be adde
i wrote:
> b) i've seen out-of-sync ebook switch behavior -- i.e., the event
> being reported (ebook open/close) exactly mismatches the
> physical condition of ebook mode. since this behavior was
> described for the lid switch in #5703 (and fixed), i'm
> guessing the ebo
It would be useful if
> > rawhide supported dimming/shutting_off the screen when no one is
> > looking at it (irrespective of whether the CPU is doing work or not).
>
> i'm sure rawhide will gain a power management solution of some
> sort. probably ohmd will be added. i w
scott wrote:
> On Sat, 2009-03-14 at 09:37 -0400, p...@laptop.org wrote:
> > i'm sure rawhide will gain a power management solution of some
> > sort. probably ohmd will be added. i wouldn't be surprised if
> > olpc-kbdshim and olpc-powerd would work fine as
button press and pops up a
> > "hibernate/suspend/yadayada/" dialog, and then your XO suspends
> > anyway :-)
>
> yeah, i kind of expected that. similar issues happen if you run
> ohmd alongside powerd as well. is g-p-m (easily) uninstallable?
Yes. Very easy to r
:-)
> >
> > yeah, i kind of expected that. similar issues happen if you run
> > ohmd alongside powerd as well. is g-p-m (easily) uninstallable?
>
> Yes. Very easy to remove.
>
> One additional point related to power management, the control panel in
> the
On Sun, 2009-03-15 at 00:37 -0400, p...@laptop.org wrote:
> scott wrote:
> >
> > > > 3. with the OLPC kernel and this olpc-kbdshim and olpc-powerd (which
> by
> > > > the way are really realy nice, thanks a million pgf!) the XO suspends
> > > > when via "lid" switch and the power button.
> > > i'm sure rawhide will gain a power management solution of some
> > > sort. probably ohmd will be added. i wouldn't be surprised if
> > > olpc-kbdshim and olpc-powerd would work fine as well, but if
> > > you'd like to test that to co
een
them pretty easily.
there's also a (very) primitive configuration utility that lets
you select the major configuration parameters. (it's dialog-based,
so it's curses-based graphics. you've been warned.)
by default, power management is only active when you're running
pgf writes:
> so: i've packaged a new version of powerd. the big change
> is that it now allows for the two modes of operation i mentioned
> last week on the list:
> dim
> sleep, screen on
> sleep, screen off
> shutdown
> or:
>
albert wrote:
> pgf writes:
>
> > so: i've packaged a new version of powerd. the big change
> > is that it now allows for the two modes of operation i mentioned
> > last week on the list:
> > dim
> > sleep, screen on
> > sleep, screen off
s
> on the XO. small improvements are difficult to implement
> quickly.
>
> since my heart is with more quasi-embedded systems than the XO's
> current incarnation, part of my goal was to do a rewrite which
> was not dependent on hald, dbus, or X11 -- power management
> shou
since my heart is with more quasi-embedded systems than the XO's
> > current incarnation, part of my goal was to do a rewrite which
> > was not dependent on hald, dbus, or X11 -- power management
> > should work well from a console screen, and be available even if
>
It's looking to us that the aggressive power management enabled on the
XO can sometimes create confusion when children are collaborating on
activities.
Take for example a turn-based game like Memorise. If a child is
waiting for their turn, they might leave the XO untouched. In that
time,
Hi,
If you want to test automatic suspends without wireless on the latest
joyride builds, here are some instructions. I measured battery life
of over 16 hours with this setup last week (with occasional wakeups):
# /usr/sbin/ohmd
# echo 0 > /sys/power/wlan-enabled
(leave the touchpad/key
Please help test joyride-2200. We'll announce a new weekly joyride on
Wednesday afternoon on this list.
Thanks,
Michael
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
On Fri, Nov 28, 2008 at 04:18:11PM -0500, Chris Ball wrote:
>Comments welcome. Are there important power management bugs that I've
>left out?
Yes; namely, finding or writing a good technical introduction to the
subject of power management as it applies to our software and hardw
On Nov 28 2008, at 16:18, Chris Ball was caught saying:
> Hi,
>
> This e-mail describes the work plan for power management during December.
> I've filed bugs for each item, so this plan is the list of bugs that
> should be fixed during December.
Thanks for putting this toge
> ... if we are able to fix all of these bugs we'll be in excellent shape
> for having a shippable-by-default automatic suspend feature in 9.1
Depends upon how inclusive a definition of "excellent" one chooses.
[I'm the guy without wireless - I'm running wired ethernet.]
A tremendous amount of pr
Michael Stone wrote:
> On Fri, Nov 28, 2008 at 04:18:11PM -0500, Chris Ball wrote:
>> Comments welcome. Are there important power management bugs that I've
>> left out?
>
> Yes; namely, finding or writing a good technical introduction to the
> subject of power ma
emaining bugs in WOL don't
affect it.
B.t.w. this should be re-phrased as ARP requests for XO's own IP address.
Ricardo,
Can you update the trac?
> * #7981 -- EC mask setting is inefficient
> * #9055 -- Create 9.1 test plans for automatic power management
>
> Bugs I will ne
ou update the trac?
Sure. This has been tested in the past with good results. I am
repeating the tests with the new improved signature wol filter and
recent firmwares and will post results to the ticket (later today)
>
>
>> * #7981 -- EC mask setting is inefficient
>>
Hi -
I've been dabbling with joyride-1572 on a g1g1 laptop for a day or
few, and have noticed the suspend feature kick in after a few seconds
of apparent inactivity. I have some questions about whether some
specific experiences with this are expected:
- that a resume operation begins only with a
We are considering disabling Automatic Power Management because of its
impact on collaboration and 3G connectivity.
What kind of battery life can we expect from an XO-1.5 with Automatic
Power Management disabled as opposed to enabled? I understand that
this can vary wildly with usage, but is
On Fri, 25 Jan 2008, Richard A. Smith wrote:
> Chris Ball wrote:
>
>> >> Can I wake up 10 seconds from now? Is there a timer in any of the
>> >> hardware that is left running?
>>
>> > Yes, but the software does not support this yet. See bug #4606:
>> > http://dev.laptop.org/ticket/4606
>
On 26/01/08 21:47 +, [EMAIL PROTECTED] wrote:
> On Fri, 25 Jan 2008, Richard A. Smith wrote:
>
> > Chris Ball wrote:
> >
> >> >> Can I wake up 10 seconds from now? Is there a timer in any of the
> >> >> hardware that is left running?
> >>
> >> > Yes, but the software does not support th
We're building a platform, and have been completely and brutally
> > transparent about our progress. Software built on our platform will
> > keep improving rapidly along a number of axes, power management being
> > one, and even more rapidly if folks jump in and help us w
Power management ideas will be discussed, categorized from "simple
matter of programming" through "good research topic", and prioritized.
Examples at the SMoP end might include:
* using the EC for timed wakeups when asked to by userspace
* inhibiting suspend when asynchro
Hi all,
upgraded to 2414 and realized that the auto power management checkbox in the
sugar control panel is unchecked even though the XO seems to show a regular
power management behavior. Is this a bug or am I missing something here
(e.g. auto power management being a different mode to what'
Very cool!
How well will this integrate with the power management systems other
distros are using? Can it become a 'Value Added' for other netbook
manufacturers?
david
On Fri, Mar 13, 2009 at 4:33 PM, wrote:
> hi --
>
> i had an itch that needed scratching,
david wrote:
> Very cool!
>
> How well will this integrate with the power management systems other
> distros are using? Can it become a 'Value Added' for other netbook
> manufacturers?
while i'd love to say i did a lot of research and prep in order
to make
behaves oddly, as gnome-power-manager also
> > > > intercepts the power button press and pops up a
> > > > "hibernate/suspend/yadayada/" dialog, and then your XO suspends
> > > > anyway :-)
> > >
> > > yeah, i kind of expected that. s
fate might be.
so: i'm hoping someone (deepak? chris?) can write up a sketch
of how they think power management, those input devices, wakeup
events, etc, will work on 1.5. direct comparison to 1.0 would be
helpful. (and of course a tie-in to specific work-to-be-done
and/or modules-to-be-writte
e causes the
>> video to go blank! Or I can wait about 80 seconds and the video
>> will go blank on its own.
> Is Automatic Power Management (My Settings, Power) enabled?
...
> I suggest the bug may be due to a conflict between Automatic
Power Management and the XV component
Hi Frank,
> Hi - I've been dabbling with joyride-1572 on a g1g1 laptop for a
> day or few, and have noticed the suspend feature kick in after a
> few seconds of apparent inactivity. I have some questions about
> whether some specific experiences with this are expected:
> - that a
> Yes, the resume operation is triggered by user input, or a wireless
> packet addressed to the host (or some battery-related events). It
> can't be triggered by anything in software unless that's organized
> ahead of time; the CPU is turned off completely in the suspend mode.
What does "organi
On Wed, 2008-01-23 at 11:47 -0800, Hal Murray wrote:
> > Yes, the resume operation is triggered by user input, or a wireless
> > packet addressed to the host (or some battery-related events). It
> > can't be triggered by anything in software unless that's organized
> > ahead of time; the CPU is tu
On Jan 23, 2008 2:47 PM, Hal Murray <[EMAIL PROTECTED]> wrote:
>
> > Yes, the resume operation is triggered by user input, or a wireless
> > packet addressed to the host (or some battery-related events). It
> > can't be triggered by anything in software unless that's organized
> > ahead of time; t
Hi,
> What does "organized ahead of time" mean?
Setting a wakeup timer before going to sleep.
> Can I wake up 10 seconds from now? Is there a timer in any of the
> hardware that is left running?
There are two timers left running. There is the Geode southbridge RTC,
which can set a wa
Hi,
>> Can I wake up 10 seconds from now? Is there a timer in any of the
>> hardware that is left running?
> Yes, but the software does not support this yet. See bug #4606:
> http://dev.laptop.org/ticket/4606
We don't *use* the southbridge RTC wakeup, but it's not strictly true
tha
On Wed, 23 Jan 2008, Chris Ball wrote:
> Hi Frank,
>
> > Hi - I've been dabbling with joyride-1572 on a g1g1 laptop for a
> > day or few, and have noticed the suspend feature kick in after a
> > few seconds of apparent inactivity. I have some questions about
> > whether some specific expe
Chris Ball <[EMAIL PROTECTED]> writes:
> [...]
> In the future, we can imagine setting wakeups programmatically, with
> the help of the Linux dynamic ticks implementation and the cpuidle
> framework -- if Frank's sugar clock has a pending wakeup in 60 seconds
> to update the minute hand of the clo
Hi Frank,
>> In the future, we can imagine setting wakeups programmatically,
>> with the help of the Linux dynamic ticks implementation and the
>> cpuidle framework -- if Frank's sugar clock has a pending wakeup
>> in 60 seconds to update the minute hand of the clock, we can set a
>
1 - 100 of 179 matches
Mail list logo
