Kernel 2.6 size increase
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Tom Rini
Power Management, sysfs plays / will play a role in finding out the order in which devices get powered down. This is important on some types of embedded devices (and arguably important everywhere).
You are contradicting to yourself.
I have participated in creation of two specialized embedded systems,
and currently going into third one.
Every system were need some specialized shutdown sequence. None of them were need power saving.
Please do not generalize your particular system to everything else.
No one needs another self-aware self-configurable software subsystem,
which intended to do the task of the engineers. Especially when this task takes 15 minutes to code.
Quoted 7 lines · Ihar Philips Filipau
Quoted 5 lines · Tom Rini
Power Management, sysfs plays / will play a role in finding out the order in which devices get powered down. This is important on some types of embedded devices (and arguably important everywhere).
Quoted 6 lines
You are contradicting to yourself.
I have participated in creation of two specialized embedded systems,
and currently going into third one.
Every system were need some specialized shutdown sequence. None of them were need power saving.
Shutdown != sleep. If you want to wake devices up again, you need to do them in the right order.
Signature · 2 lines
Tom Rini http://gate.crashing.org/~trini/
Quoted 4 lines · Tom Rini
Shutdown != sleep. If you want to wake devices up again, you need to do them in the right order.
You didn't get my point.
My appliances do not need sleep/shutdown at all. Not every embedded system is a handheld ;-)
Shutdown was smth like:
# mount / -o ro; sync; lcd-off; \
dd if=/dev/zero seek=0xBYE of=/dev/port
For a long time it was shell script :-)))
Quoted 8 lines · Ihar Philips Filipau
Quoted 3 lines · Tom Rini
Shutdown != sleep. If you want to wake devices up again, you need to do them in the right order.
You didn't get my point.
My appliances do not need sleep/shutdown at all. Not every embedded system is a handheld ;-)
That certainly is true, yes. They might want to power things down when the user isn't there (or maybe they don't, I don't know what you're making :)). And I did originally say 'some'.
Signature · 2 lines
Tom Rini http://gate.crashing.org/~trini/
Quoted 10 lines · Tom Rini
Quoted 4 lines
You didn't get my point.
My appliances do not need sleep/shutdown at all. Not every embedded system is a handheld ;-)That certainly is true, yes. They might want to power things down when the user isn't there (or maybe they don't, I don't know what you're making :)). And I did originally say 'some'.
Can you imagine teapot?
State of your system - on/off. Power saving as done by user herself:
power is consumed only when user want to boil the water ;-)
Two devices I was working on were little bit more complicated and I
had internal UPS to be able to handle power offs/fails gracefuly (like switching off of LCD + save of the mechanics state).
As for me - I already expressed my point on subject: we should fix
compiler and language (C's inline is definitely not ehough to express our intentions to compiler). That's the compiler should be optimized to gain space for performace or gain performance for space.
And sure kernel should be more configurable too.