Latest revision as of 23:06, 16 December 2009

Contents

Description

Every user has behavioral patterns. Behavioral pattern is the
sequence of actions, running applications and so on. Some of these
patterns are common and the others are individual. Knowing the
patterns the program (that should be developed as the result of the
project) can optimize the OS's behaviour to reduce energy consumption,
response time and etc.

For example (common pattern), if user starts a video in the full-screen
mode the program can automatically suspend some subsystems (like USB or
CD/DVD-rom). Also the program can "hibernate" unused applications.
Another example (individual pattern): if the user usually runs OpenOffice.org
after the game or two of Mahjong, the program can automatically prepare the
OS to quick start of the OOo.

Comments

Alexander Voytov wrote:

QNX claims real time power supply management for its car application
embedded solution.

On the PC like laptop/desktop there is the ACPI standard which version
3 I'm not aware is implemented by anyone on any platform. The problem
with the PS(power supply) control is - it is an analog device in the
most common case, but there is a growing market of the digital control
PS. Means, you can control such devices like any other real time
interfaces.

I'm not aware about the PS behaviour control implementation, except
the RF board design. On majority the RFID boards there is a signal
strength pin to power up the board in case the RFID signal is
detected. This is a proprietry design to wake up all board drivers and
interfaces for converting an oncoming analog RF signal into, for
instance, the USB or a serial packet. On some such devices the Linux
kernel is implemented, on majority I'm aware about - the home growth
SW state machine.