Not an issue of voltages, I think, but multipliers; you can run the DSP at 2/3 or 1/3 the CPU speed, but an absolute max of ~250; so your options for 400 MHz are use the 2x multiplier and go 266 (overclocking past spec), or drop to the 1x for 133 (pitiful performance)...

It all depends what tasks the DSP is trying to keep up with; in most cases the 400/133 should work. The cool thing would be to try to make a new governor that actually knows about DSP usage, and doesn't cap it unless the extra DSP is needed. (And jitters between 400/133 and 333/222 when both are in high usage, so audio and video buffers stay full.)

But since the N800 (AFAIK) doesn't have any video codecs implemented on DSP, and audio is performed adequately at 133 MHz, that seems a more useful setting for most purposes. (Maybe it'll be an issue, if we get A2DP on the DSP; MP3 decoding and A2DP re-encoding might cram 133 MHz?)

I tried this out and it was great, but I prefer the full versions of most things on the n810 instead of the mobile versions. Not to mention it adds to the wow factor of the device.

BTW, these tweaks worked out great. The sysctl ones do seem to make things snappier.

BTW, do you know how I can get a customboot script (S99customboot.sh) to load the xmodmap file?

It seems to do everything else I asked it to (sync the hardware clock/kernel clock, etc) and the logfile shows that xmodmap loaded, but the key bindings never loaded or held.

I tried straight up xmodmap /home/user/xmodmaprc and
neither seem to work. I even tried an @reboot in my cron. Xmodmap will run from either root or userspace and load the xmodmaprc file.

Excellent... thanks for that.

Actually, does anyone know if there are any system ones we can stop if we dont use them such as Obexsrv. Since I dont use bluetooth file sharing it might be an option. But where do I go to read up on what each one does?

I'm dreaming of having 50 meg free after a boot. Again for caching and making things run smoother/faster.

Any news on a .deb or some other way to easily apply these optimizations?

i second mikeb1973 request...even one that would have to be run from xterm...

Question is with Diablo out, do the same tweaks even apply, or are there new/better ones for under Diablo.

well im trying some off the brower tweaks...seem to help...

I've just applied most of the stuff to my diablo install and I would say they are still quite applicable. Maybe I should get off my butt and package up a few of them ( now that I know how )

i want gonna pester you personally i figured you'd get around to it.....

So, I'm trying to figure out a way to boost the speed of a loop-based (image file) chroot, without endangering the user's tablet too much. I figured I could safely do the mmcqd renice:

I would also like to all-but-disable metalayer-crawler (disabling it might cause problems for some); perhaps renicing it to some very high number? Is there any way to fence off places to the crawler? I don't want it wandering off down the corridors of my chroot, because the media cards are mounted under the chroot as well, and they may look like second copies of the same files...

Also, would you say the swap parameters might be safe enough to bump higher when running the chroot?

I notice that there may be a speed reduction when running from an SD partition and also trying to chroot to another SD partition or loop device. Perhaps because there's some problem trying to quickly read from two partitions on the same device? Is that possible?