Is the chinook sdk available, are the kernel sources??

SDK seems to be available: http://maemo.org/development/sdks/ma..._beta_sdk.html

no, but in theory for compiling modules you could do with 2.6.21 from http://muru.com/linux/omap/

But of course the easiest thing is to hack something else instead and wait a month or so for 2008 firmware and real N8x0 kernel release :-)

strongly agree, but somekind of dissappointed

Agree with Fanoush... The real benefit would be for OS2007, and it is at its end of life... It would need to add cpu driver (omap), which likely is not just easy hack. (But I could be wrong...)

While I agree, it would be nice to have it ready. No time like the present

There's a link to a power management presentation from July in this post on the maemo-developers mailing list:
http://lists.maemo.org/pipermail/mae...ly/010821.html

From the doc linked in that post, here's confirmation of the four speed states on the OMAP2:
So Nokia may have chosen 330MHz initially for two reasons:

• Battery life (330MHz instead of 400MHz for the ARM core)
• DSP performance (the DSP is clocked highest with the ARM @ 330MHz)

Apparently there is an upper limit to the DSP core frequency. The DSP clock is probably derived off of the ARM clock, and the available dividers are likely the reason the DSP ends up running at a lower frequency with the ARM at 400MHz. Although I haven't looked too closely, the DSP only seems to be used for audio decoding (MP3, AAC, etc.) Hopefully there will be enough MIPS with the DSP running at the slower speed. One place the higher ARM speed is required (video playback) is also where audio decoding may require a lot of DSP MIPS. Obviously a balancing act, which may provide another explanation of why Nokia took so long to release this.

A more interesting question is whether the ARM core can be clocked higher than 400MHz with the available OMAP register settings. TI does not seem to release their real technical documentation to the public. Anyone have this documentation to share, or some hints where it can be found?

Yes, read whole thread you linked, check this one.
http://lists.maemo.org/pipermail/mae...ly/010824.html
They did for previous boards/chips 5910 (similar/same as 1510) and 5912 (1610 or maybe 1710). Most HW registers for old stuff are probably backwards compatible. Also Linux kernel source should be good reference. Either the code is already in mainline or OMAP tree or we must wait for Nokia, they will give us that once they release 2008 firmware.

BUMP... Now when everybody has the OS2008... you can try this again...

How about underclocking

Nokia-N800-:/# cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
driver: omap
CPUs which need to switch frequency at the same time: 0
hardware limits: 165 MHz - 400 MHz
available frequency steps: 165 MHz, 266 MHz, 330 MHz, 400 MHz
available cpufreq governors: conservative, ondemand, null, powersave, performance
current policy: frequency should be within 165 MHz and 400 MHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 400 MHz (asserted by call to hardware).



Nokia-N800-:/# echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



Nokia-N800-:/# cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
driver: omap
CPUs which need to switch frequency at the same time: 0
hardware limits: 165 MHz - 400 MHz
available frequency steps: 165 MHz, 266 MHz, 330 MHz, 400 MHz
available cpufreq governors: conservative, ondemand, null, powersave, performance
current policy: frequency should be within 165 MHz and 400 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 165 MHz (asserted by call to hardware).





Nokia-N800-:/# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
conservative ondemand null powersave performance

EDIT
It does seem to set itself back to original "performance" setting