The thing is, that using Raspberry Pi exclusively, You should mirror Your content from N900 (documents, photos, programs, etc). Not to mention things like Truecrypt encrypted partitions, if You work on those. Also, for most "productivity" things, N900 MPU is *much* better - it's not a matter of raw mhz value, check SoC specification. Raspberry Pi SoC is *really* strange thing. I agree that it performs well when it comes to DSP, though.

As we have our N900's always with us, we tend to work on it on the go - sitting in train, for example, there is no sane way to work on Raspberry Pi (no screen). Using Pi exclusively, we would need to sync everything we did on N900, when - later - we have access to monitor with DVI input. in practice that would mean - most of the times - more overhead due to rsyncing, than just using N90 0with it's internal screen and keyboard to continue work.
---

What we want to achieve - by any means possible - is to be able to view N900's Maemo and ED things in "big screen" in good quality (through HDMI or DVI), using Raspberry Pi as intermedium. "Period." It require setting up correct system on Pi, and that's ok - we will probably use Pi for other means as well - but, considering proper set of script, settings etc, it should be as hassle-free to connect n900 this way, as possible (of course, after initially setting things up).

/Estel

// edit

@javispedro
do it understand correctly, that You mean that we can use x11vnc on N900, and udlfb on Raspberry Pi, connected to DVI/HDMi monitor, and that would cause usage of DisplayLink protocol, which is meant especially for high-bandwidth (like in local network), low-latency connections? sounds cool, need to test it ASAP.