Ok, long time reader first time asker on this parcticulair stack-exchange.
I am rather new to electronics, I've done some simple projects like Blinking Lights, alarms that go on when its dark and a Joystick Gamepad (with Arduino).
However, I am experianced in system programming, I've written a bootloader (x86) for fun, read assembler language for a living and have hacked some code for kernel modules.
For my most recent projects I got rid of the arduino and used a breadboard to build the entire board (same setup as the arduino though). I've created a project, got the breadboard prototype to work and now I am ordering a number of PCBs (seeedstudio) to get the real prototype going.
While I am waiting for these boards and the components to arrive I've started a project with the RaspberryPI, created a embedded linux for it and I've been playing with the GPIO. Now I wonder, how hard is it (and what is required) to breadboard a raspberrypi so I can eventually also get my own boards created for beefier projects.
TL;DR)
What should I learn about before I can assemble a RaspberryPi on my Breadboard? As I can't imagine it is as easy as breading the Arduino
Note: I've read, http://arduino.cc/en/Main/Standalone
Best Answer
I've been dabbling in electronics since the 1970s and had products used in nationwide broadcasting chains, reviewed (sometimes favourably!) in hi-fi magazines and (possibly soon) headed into orbit, and I would still consider breadboarding a Raspberry Pi a major project.
Find a middle ground : take a look at an ARM CORTEX CPU running at 50 or 100 MHz and learn to use that. Then when that is second nature, consider taking another look at the Raspberry Pi (or whatever has replaced it in the meantime). A good starting point is the TI Launchpads (Stellaris, now Tiva) or Hercules for 100 MHz and high-reliability hardware. Or similar processor devkits from ST Micro or NXP. When you grow beyond the Launchpad board itself you will have experience with a more advanced CPU system than the traditional Arduinos, and it's in a package which is much easier to breadboard than the Raspberry Pi. (And at this level, "breadboard" really means layout your own PCB).
You won't even get a datasheet for the R-Pi's processor without serious negotiations (probably involving six digit numbers) with Broadcomm.
Alternatively, use the R-Pi as a component - a complete subsystem in your design that removes the need to repeat a LOT of engineering and lets you concentrate on your specific application; focus on what makes your hardware + software app unique.