This project could bear a title like "all your Kindle are belong to R-Pi."
I have a Kindle 3 on which I am root. See this guide:
I would like to do four things:
(1) I would like to harness the Kindle's display for use by the R-Pi,
(2) I would like to harness the Kindle's storage for use by the R-Pi,
(3) I would like to harness the Kindle's wifi chip for use by the R-Pi,
(4) I would like to harness the Kindle's CPU + RAM for use by the R-Pi.
The "pi in the sky" ideal solution would be a distributed operating system that abstracts away all the nasty details, but that doesn't exist for this application (AFAIK...).
The next best thing would be to set these things up over a USB network. I gather X has support for (a portion of) this functionality, but I have no idea how to do any of it.
But, is doing this in X the right thing? People have VNC'd Kindles to various computers, but that seems wrong to me for a variety of reasons which should be obvious. The R-Pi and Kindle are both ARM boxes, they are both running Linux, they are both Xorg capable. However, it would be nice to have the R-Pi's TTY pop up on the Kindle screen if connected at boot.
It seems to me the Kindle is the ideal complementary device to the R-Pi. It is cheap ($80US for the new ones), low power, and easy to hack. Getting a plug & play solution to at least the display and wifi problems working (1 and 3 above) would be huge. Shared storage would be grand. CPU sharing (even if it's an MPICH2 type thing) would be epic.
By "plug & play" I mean the startup sequence should be something like:
(1) run ./rpi in the Kindle shell,
(2) boot the R-Pi with it connected to Kindle over USB,
So, could you folks who know lots more about this stuff than I do tear this idea apart? Pointers to relevant documentation would be a big help! As is likely apparent I know very little about networking.