Hi,
Am Samstag, den 21.01.2006, 12:38 + schrieb Andrew Flegg:
> On 1/21/06, Danny Milosavljevic <[EMAIL PROTECTED]> wrote:
> >
> > What about just warning the user when he tries to power off?
> >
> > [ Poweroff but events are pending
> > [
> > [ The next event comes up on xx.xx. at xx:xx.
On 1/21/06, Danny Milosavljevic <[EMAIL PROTECTED]> wrote:
>
> What about just warning the user when he tries to power off?
>
> [ Poweroff but events are pending
> [
> [ The next event comes up on xx.xx. at xx:xx.
> [ Are you sure you want to power off and possibly miss the alarm?
> [
> [ [Oo
Hi,
Am Montag, den 16.01.2006, 14:24 +0200 schrieb Igor Stoppa:
> On Fri, 2006-01-13 at 16:11 +0100, ext Nils Faerber wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Igor Stoppa schrieb:
> [snip]
> > > Obviously they have different wakeup latencies but all of them are
> > > i
On Fri, 2006-01-20 at 16:17 +0200, Riku Voipio wrote:
> On Wednesday 18 January 2006 15:07, Igor Stoppa wrote:
> > The price for it is that we had to fix drivers and applications so that
> > they would behave decently, without keeping resources (clocks)
> > constantly allocated and without generat
On Wednesday 18 January 2006 15:07, Igor Stoppa wrote:
> The price for it is that we had to fix drivers and applications so that
> they would behave decently, without keeping resources (clocks)
> constantly allocated and without generating unnecessary activity.
The problem is 3rd party developers
Hi,
I see the discussion moving away from the original subject of Alarm
management to device management.
it wasn't expected, but it's fine, let's just change subject.
So please let me spend a few more words on power 770 states and device
states in general.
As I wrote in another mail, we really did
On 1/17/06, Weinehall David (Nokia-M/Tampere) <[EMAIL PROTECTED]> wrote:
We already do the power saving part, we already have all the positiveside effects of keeping alive -- but *if* the user wants to do a propershutdown, which will allow him to keep the device alive even longer than
usual -- let
On mån, 2006-01-16 at 11:52 -0500, ext Dave Neuer wrote:
> On 1/16/06, Igor Stoppa <[EMAIL PROTECTED]> wrote:
> >
> > That's not really desired in a consumer device.
>
> I can see I'm going to run a risk here of alienating myself early from
> the Nokia employees on the list, as I keep coming to th
Weinehall David (Nokia-M/Tampere) wrote:
We already do the power saving part, we already have all the positive
side effects of keeping alive -- but *if* the user wants to do a proper
shutdown, which will allow him to keep the device alive even longer than
usual -- let them. It's not going to hu
On mån, 2006-01-16 at 20:46 +0100, ext Frantisek Dufka wrote:
snip]
> Why not let users shutdown easily? Because you keep the state and don't
> need to boot the device through tons of /etc/rcx.D/* (and do it in
> advance without user noticing anything) to handle single alarm and then
> shutdown i
On 2006-01-16, Dave Neuer wrote:
>
> On 2006-01-16, Igor Stoppa wrote:
> >
> > On Mon, 2006-01-16 at 17:21 +0200, ext David Weinehall wrote:
> > >
> > > A mechanism for wake-up from power-off exists (yes, it's a bit sucky,
> > > so we'll have to have a workaround for alarms >24h into the future,
Weinehall David (Nokia-M/Tampere) wrote:
No in PalmOS off is not off. On Tungsten T2 you can set it to be waked
up by initiating bluetooth connection with it when it is 'off'. You can
also schedule alarm procedure which gets executed and the display is
even not waked up if you wish. Unlike wi
On 1/16/06, Igor Stoppa <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-01-16 at 17:21 +0200, ext Weinehall David (Nokia-M/Tampere)
> wrote:
> >
> > A mechanism for wake-up from power-off exists (yes, it's a bit sucky,
> > so we'll have to have a workaround for alarms >24h into the future,
> > but at lea
On 1/16/06, Igor Stoppa <[EMAIL PROTECTED]> wrote:
>
> That's not really desired in a consumer device.
I can see I'm going to run a risk here of alienating myself early from
the Nokia employees on the list, as I keep coming to this same point
when reading a lot of the posts here, and think it stil
On Mon, 2006-01-16 at 17:21 +0200, ext Weinehall David (Nokia-M/Tampere)
wrote:
> On mån, 2006-01-16 at 15:58 +0100, ext Frantisek Dufka wrote:
> > Nils Faerber wrote:
> > > I also guess that most
> > > Palms and alike behave the same - off is off. Only exception from that
> > > rule I know of are
On Mon, 2006-01-16 at 14:24 +0100, ext Nils Faerber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Igor Stoppa schrieb:
> > On Fri, 2006-01-13 at 16:11 +0100, ext Nils Faerber wrote:
> > Igor Stoppa schrieb:
> >> [snip]
> >>Obviously they have different wakeup latencies but all of th
On mån, 2006-01-16 at 15:58 +0100, ext Frantisek Dufka wrote:
> Nils Faerber wrote:
> > I also guess that most
> > Palms and alike behave the same - off is off. Only exception from that
> > rule I know of are (some) mobile phones.
>
> No in PalmOS off is not off. On Tungsten T2 you can set it to
Nils Faerber wrote:
I also guess that most
Palms and alike behave the same - off is off. Only exception from that
rule I know of are (some) mobile phones.
No in PalmOS off is not off. On Tungsten T2 you can set it to be waked
up by initiating bluetooth connection with it when it is 'off'. You
Le lundi 16 janvier 2006 à 14:24 +0100, Nils Faerber a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Igor Stoppa schrieb:
>
> >> These small details make the difference between a "device for hackers
> >> only" and a device that can leverage the benefits of running linux and
> >> ye
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Stoppa schrieb:
> On Fri, 2006-01-13 at 16:11 +0100, ext Nils Faerber wrote:
> Igor Stoppa schrieb:
>> [snip]
>>Obviously they have different wakeup latencies but all of them are
>>insignificant, when compared to the delay that would be introduced
On Fri, 2006-01-13 at 16:11 +0100, ext Nils Faerber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Igor Stoppa schrieb:
[snip]
> > Obviously they have different wakeup latencies but all of them are
> > insignificant, when compared to the delay that would be introduced by a
> > tradit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Stoppa schrieb:
> On Thu, 2006-01-12 at 15:55 +0100, ext Florian Boor wrote:
>>Igor Stoppa wrote:
>>>Only Retu can wake up the device from poweroff state at a preset time;
>>>unfortunately this is the time resolution that it canprovide. In order
>
On Thu, 2006-01-12 at 15:55 +0100, ext Florian Boor wrote:
> Hello,
>
> Igor Stoppa wrote:
> > Only Retu can wake up the device from poweroff state at a preset time;
> > unfortunately this is the time resolution that it canprovide. In order
> > to extend alarms and events scheduling one could have
Hello,
> That's using a HW timer and we already do the same. On the 770 the Omap
> RTC is not capable of waking up the device from power off, so it is out
> of scope for a 770 specific discussion.
waking up the device from power off would take some time anyway. So it might be
necessary to deal wi
Hi,
Devesh Kothari wrote:
> Great this is feedback I was looking for. Now just to bring on same page
> again
>
> First the end user use cases
> 1. An application e.g Calender or task wanting to alart and notify the
> user of scheduled events. This notification should have a certain
> accepted gra
Hello,
Igor Stoppa wrote:
> Only Retu can wake up the device from poweroff state at a preset time;
> unfortunately this is the time resolution that it canprovide. In order
> to extend alarms and events scheduling one could have the daemon
> scheduling periodic wakeups (every 24h) till the real ala
On Thu, 2006-01-12 at 10:55 +0200, Devesh Kothari wrote:
> Great this is feedback I was looking for. Now just to bring on same page
> again
>
> First the end user use cases
> 1. An application e.g Calender or task wanting to alart and notify the
> user of scheduled events. This notification should
Great this is feedback I was looking for. Now just to bring on same page
again
First the end user use cases
1. An application e.g Calender or task wanting to alart and notify the
user of scheduled events. This notification should have a certain
accepted granularity and delivery promise
- Resolu
On Wed, 2006-01-11 at 20:20, ext Simon Budig wrote:
> Kimmo Hämäläinen ([EMAIL PROTECTED]) wrote:
> > We have also other places where multiple simultaneous programs would
> > screw things. Usually this can be avoided by the fact that the user can
> > only use one application at a time.
>
> Oh r
On Wed, 2006-01-11 at 11:35 -0800, ext Jason Mills wrote:
> A few items:
>
> 0) The RTC subsystem is served off a chip known as "Retu". Most of the ASICs
> on the Nokia 770 board seem to have nice nordic names to them. :-)
>
>
> 1) The RTC subsystem only supports one future alarm event, and that
On 1/11/06, Andrew Flegg <[EMAIL PROTECTED]> wrote:
> On 11/01/06, Kimmo Hämäläinen <[EMAIL PROTECTED]> wrote:
> >
> > I assume it will sleep most of the time and poll once in a minute
> > (according to man page).
>
> Polling once a minute is much too often, though! The daemon (even if
> it's crond
A few items:
0) The RTC subsystem is served off a chip known as "Retu". Most of the ASICs
on the Nokia 770 board seem to have nice nordic names to them. :-)
1) The RTC subsystem only supports one future alarm event, and that event may
not be more than 24h59m from "now". Maximum alarm granularity
Kimmo Hämäläinen ([EMAIL PROTECTED]) wrote:
> We have also other places where multiple simultaneous programs would
> screw things. Usually this can be avoided by the fact that the user can
> only use one application at a time.
Oh right. "Our System is broken anyway, so lets add more broken stuff."
On Wed, 2006-01-11 at 19:40, ext Ralph Giles wrote:
> On Wed, Jan 11, 2006 at 07:33:41PM +0200, Kimmo Hämäläinen wrote:
>
> > > You'd have to hack a lot around crontab to enable all this and I doubt
> > > that would be significantly less error prone than implementing that
> > > stuff e.g. in th
On Wed, 2006-01-11 at 19:05, ext Florian Boor wrote:
> Hi,
>
> Kimmo Hämäläinen wrote:
>
> > Looking at crontab(5) man page, cron allows you to execute a program
> > once in startup, so you could start some kind of daemon like that.
>
> that might be an option... as soon as we have cron which
On Wed, Jan 11, 2006 at 07:33:41PM +0200, Kimmo Hämäläinen wrote:
> > You'd have to hack a lot around crontab to enable all this and I doubt
> > that would be significantly less error prone than implementing that
> > stuff e.g. in the Desktop application or a new demon specific to that
> > task.
>
On Wed, 2006-01-11 at 18:50, ext Simon Budig wrote:
> Kimmo Hämäläinen ([EMAIL PROTECTED]) wrote:
> > I guess the 'API' is crontab(1) + crontab(5). It has probably been
> > tested in the course of time and proven good and stable.
>
> Uh, not if you have potentially multiple programs simultaneou
Hi,
Simon Budig wrote:
> I'd love to have an API call that enqueues an alarm at a specific time
> (maybe even with a specific sound, but I doubt that it should provide
> any dialog facilities, that would make it quite complex) that calls back
> into the application via dbus. That would make it pos
Hi,
Kimmo Hämäläinen wrote:
> Looking at crontab(5) man page, cron allows you to execute a program
> once in startup, so you could start some kind of daemon like that.
that might be an option... as soon as we have cron which is currently not
available.
> You could have a shell script launched
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Flegg schrieb:
> On 11/01/06, Kimmo Hämäläinen <[EMAIL PROTECTED]> wrote:
>
>>I assume it will sleep most of the time and poll once in a minute
>>(according to man page).
>
> Polling once a minute is much too often, though! The daemon (even if
Kimmo Hämäläinen ([EMAIL PROTECTED]) wrote:
> I guess the 'API' is crontab(1) + crontab(5). It has probably been
> tested in the course of time and proven good and stable.
Uh, not if you have potentially multiple programs simultaneously
modifying the crontab. One faulty program could mess up your
On 11/01/06, Kimmo Hämäläinen <[EMAIL PROTECTED]> wrote:
>
> I assume it will sleep most of the time and poll once in a minute
> (according to man page).
Polling once a minute is much too often, though! The daemon (even if
it's crond) should get told, possibly over DBUS, when a scheduled
event is
Hi,
On Wed, 2006-01-11 at 17:12, ext Florian Boor wrote:
> Hi,
>
> HimKimmo Hämäläinen wrote:
>
> > Doesn't Glib has this kind of functionality already?
>
> you can have recurring events with glib, yes... but that involves that you
> have
> the application running all the time. In combinati
Hi,
HimKimmo Hämäläinen wrote:
> Doesn't Glib has this kind of functionality already?
you can have recurring events with glib, yes... but that involves that you have
the application running all the time. In combination with the fact that you
can't have custom software packages starting up some d
On Wed, 2006-01-11 at 14:00, ext Florian Boor wrote:
> Hello!
>
> Devesh Kothari wrote:
> > I am currently looking for what developer requirements would be from
> > such an Alarm/Notifier interface. Specially lot of developers working on
> > applications which need to schedule events and notificat
Hello!
Devesh Kothari wrote:
> I am currently looking for what developer requirements would be from
> such an Alarm/Notifier interface. Specially lot of developers working on
> applications which need to schedule events and notifications like PIM
> aplications need this functionality, and it is ju
On 1/10/06, Devesh Kothari <[EMAIL PROTECTED]> wrote:
> I am currently looking for what developer requirements would be from
> such an Alarm/Notifier interface. Specially lot of developers working on
> applications which need to schedule events and notifications like PIM
> aplications need this fun
47 matches
Mail list logo
