[shr-u] wakeuptime, was Re: 2.6.31 is out, where is my ultimate kernel?

[Al Johnson]

On Tuesday 15 September 2009, Russell Dwiggins wrote:
> I'm still a bit confused.  I'm in the same boat with others here where it
> takes between 3 and 4 rings before I can take any action on the incoming
> call.  (shr-u and u-boot, both recently updated)
>
> What is the condition that allows one to take action on a call ~1 ring, and
> how does the end user get to that point?  I think there are some who will
> point to Qi as a part of the solution, but I understand that this is a
> faith-based discussion. ;) I'd prefer to remain with u-boot for now until
> the suggested kexec kernel shows up to allow me to directly select the
> partition I wish to boot from.

You need to reduce the log level. The best way is to do it in the kernel 
parameters as this will also help with the boot time, but it can be done at 
runtime as well, so you could add it to an init script. Log level 4 gets rid 
of almost everything but should still give something useful with errors, while 
0 will stop it entirely. You could pick something in between too.

For the kernel parameters you need to edit your uboot environment. Add either 
'quiet' or 'loglevel=n' where n is the desired loglevel. quiet gives loglevel 
4. See:
http://wiki.openmoko.org/wiki/Bootloader_commands#Environment

The runtime method is described on the shr tweaks page:
http://www.shr-
project.org/trac/wiki/Tweaks#majorreallymajorspeedupofsuspendandwakeup