Slashdot Mirror
What is Open Source Hardware?
ptorrone writes "In their piece 'What is open source hardware?', MAKE magazine divides up electronic hardware into layers, each of which has different document types and licensing concerns: Hardware (mechanical) diagrams, schematics & circuit diagrams, layout diagrams, core/firmware, software/API — each layer has an example provided and links to many of the open source hardware projects currently being worked on."
OpenSPARC is available from Sun Microsystems. The SPARC architecture is still highly relevant. Open source hardware projects like this are worth noting.
One very interesting example of open-source hardware is the Free Telephony Project.
David Rowe, the author has almost single-handedly designed an embedded computer using a blackfin processor combined with FXO/FXS (PSTN lines) chips to produce an extremely low-cost PBX running uclinux and asterisk. Recent posts indicate he's also close to producing a T1 interface as well. The amazing thing about this project is how open it all is. The cirucuit design, and layout for all of the boards are open. Also, he's committed to using only open-source software to do the design (and contributed a number of enhancements back to these projects, such as pcb). Not to mention also developing the uclinux based distribution, astfin, as well as a number of custom modifications to asterisk itself to use some of the Blackfin's special DSP capabilities.
You have a fab that can crank out a motherboard to order. A web page lets you pick the features you want, and then it arrives via overnight shipping.
If you care to sell your soul for rock 'n' roll, you can opt for the various DRM choices.
Maybe it arrives as a bag of chips, and you solder it yourself.
Interesting posibilities.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
hmm... now about that open source laser lithography machine...
I'm still waiting for McDonalds to open the source code to their "special" sauce.
The preferred document formats don't make sense. Distributing a schematic diagram as an image (pdf, png, etc.) is like distributing a program as an object file. In both cases modifying the item is nearly impossible. Schematic diagrams should be distributed in a format which a schematic editor, such as geda, can read. This is the electronic equivalent of source code. The same thing goes for printed circuit board layouts: just the image is not sufficient.
there's no limit to what you can open source. At some point, it ceases to be worthwhile. For instance, I could build the occasional part for my hot rod. In theory there's nothing to stop me from digging and smelting my own ore and really building a car from scratch. Obviously it isn't going to happen though. There are practical limits on what it's worthwhile to open source. Yes you can open source any design but if nobody builds that design then, what's the point?
http://www.opencores.org/ has quite a few hardware designs (mostly RTL) ranging from cryptographic engines to complete processors. They were also instrumental in developing Wishbone, a completely open SOC bus architecture, akin to something like ARM's AMBA. IIRC you can also buy a pack of cd's which contain open-source or free-of-charge EDA software.
I'm not sure if anybody's said it explicitly, but a hardware equivalent to SourceForge would be a great asset to the community, where people can share RTL, schematics, PCB and chip layouts, and so forth.
AFAIK, SPARC is the *only* open source processor.
Share time!
It is something that very, very few people will ever care about.
The schematics for the paper clip are widely available, and easily cloned, and it runs the open source uBendTo OS!
-
Apoligies for bad joke in advance, apoligies for bad spelling come later.
It will be harder to impose policeware. Trusting your computer not to spy on you for someone else (be it criminal or not), is an equation of control. Open source hardware + open source software = nearly zero government leverage. Expect legislation concerning this if this technology takes off.
Still, using geda would definitely help. Shame so few people use it. Perhaps a something like a Protel to geda converter would be a GoodThing.
Engineering is the art of compromise.
The open source rapid prototyper: http://www.fabathome.org/wiki/index.php?title=Main _Page
No, you have that right now.
Every hear of Pad2Pad.com?
If you can do the layout, they'll make your board for you. Yes, it is kind of expensive for hobby projects, but for a computer motherboard it's not *terribly* bad. A commercially made motherboard is still cheaper, but I guess if you want something without DRM, you're always welcome to implement it yourself.
Now, the only problem is that implementing and debugging a computer from scratch could be a rather time consuming undertaking. But, if you've got the time, there are places who will build it for you, whatever *it* is.
The society for a thought-free internet welcomes you.
Here is the biggest Open Sores.
I hope this helps the criminal investigation of the world's largest crime syndicate.
Patriotically,
K. Trout, C.T.O.
Im looking for a bento box, it cant be pinku (thats japanese for pink) or any girl color. It has to be
of 2 or more kotoba (thats japanese for 2 compartments) and has be be chibi (small) sized. And
has to be really kawaii (cute). Also It has to be about 10-20 bux. And you have to post pics of it
first (i want to make shure it's kawaii [cute]). And it would be nice if it came with matching
chopstick holder (WITH chopsticks). OH! and it CANNOT have any cartoon pictures, or be made
out of plastic. It has to be made of ceramic, or something like that. Also it would be nice if it was
made in japan. and not in china or corea (korea) or whatever. I have found a bento box similar to
the one im describing in e-bay, but it was 1 kotoba, and i dont want my gohan (rice) to touch my
other things (it can get wet and i would not like that, plus 2 compartments looks more kawaii)
Sure, you can open source hardware, but only in a BSD-style way. Chumby is trying to share-alike their hardware design, but that doesn't work as well as GPL for software or CC Share Alike for something like a work of fiction because while a schematic or PCB can be copyrighted, the netlist implied therin cannot be protected. With dense ASICs/SoCs where most of the design complexity is on-die rather than in the connections on the PCB and the registers in the chip are freely documeted, reverse-engineering isn't hard.
Chumby's response to this is (parphrasing) "fine hook stuff up to the chumbilical by looking at the MX.21 reference design and tracing connections and you won't be subject to our hardware license," but I wonder if they'll really be hands-off if an accessory developed without agreeing to their hardware developers' license is commercially successful. They're selling the hardware at slim margins and hoping to make profit on the service.
Ronja
The schematics for electronics and mechanical design are available, including in enditable source form.
SJW n. One who posts facts.
Ok, I like Sun and all, and I don't disagree with any of the points you're raising, but how much is Sun paying you to be a Sun fanboy? Perhaps I could get in on this payola action..
I'm surrounded by engineers with the capability to produce open source computers, but...
Nobody has the time or interest.
Yes, I (among many) could design and implement a computer complete from the gate-level design all the way up to the compiler and operating system.
Ironically, now that I have the knowledge, I don't have the time to work on it. It gets worse:
If I did build my own computer, friends and family would inevitably ask, "So why did you spend $(Multiple thousands) for a computer slower than the $299 Sam's club special?", and "Isn't that just an expensive hobby? - you don't really expect people to buy a 1 GHz ARM machine, do you?" etc..
I would like to work on open source hardware. I do have experience porting Linux to new architectures. But sadly, I think something about corporate america just takes away the passion from the discipline. Since I started programming more than 10 years ago, I have met only one person who was passionate enough about it to do it outside of work. And you know what he did? - mods for a game. Nothing really serious or interesting.
It's not that there is a lack of talent. Rather, apathy is fatal to open source. And we need to come to terms with the fact that the overwhelming majority of those with the knowledge to do something disruptive, to use their skill to change their world for the better, choose just to go home at night and watch tv.
They have no geek passion. They are irrelevant to the discipline. And they are exactly what Corporate America wants them to be.
The society for a thought-free internet welcomes you.
I was discussing this with some friends on the web.We need better software tools to aid in cooperation.
We need a web based schematic editor.
No bells and whistles are needed just an editor where you can pick basic components and chips with varying numbers of pins.
A wiki would be good too but it would be a lot easier to edit the schematic on the webpage and save it to the web and/or your hard drive.
I would love to help but I'm not great at programming.
Maybe someone could suggest something ?
I admit I haven't really been paying attention to SPARC recently.
Can anyone fill me in on what its performance is like compared to x86 these days, when running Linux or Unix (Solaris)? (I don't think MS even supports Windows on non-x86 anymore, except perhaps Itanium and it's probably near-EOL anyway.)
There seemed to be a lot of buzz about the Niagara stuff a while back, and how amazing the performance/watt was going to be, and then it seemed to evaporate. Did something happen, or was that just the fanboys moving on to something else shiny? (And is Niagara open-source/open-architecture like the more basic SPARC processors?)
I've always been a big fan of RISC, since back in the early 90s; I think it's sad that we're fast approaching a monoculture, although there's some solace, I suppose, in the fact that with decreasing process sizes, you can now tack the x86 instruction set onto almost any real processor you want. But it certainly seemed like there were more avenues for performance being investigated back when you had IBM with Power, DEC with Alpha, Sun with SPARC, SGI with MIPS, HP with PA-RISC, and probably a bunch more that I've forgotten.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Years ago, when I was single and could afford toys, I bought a Blaupunkt Tuscon head unit - at the time (1987), it was the absolute best car stereo AM/FM/Cassette head unit you could buy. Could even receive AM Stereo from the one station in town that broadcast it. Set me back $750, and I still had to get an amp for it, since it only had line-level outputs.
But...
It came with a COMPLETE set of schematics, including not just block diagrams, but actual component values and chip numbers. Given that schematic, I could have build a complete new unit. I was floored. I almost wanted to try it, just to see if I could - but couldn't imagine trying to build the whole thing on breadboard with my trusty Radio-Shack soldering iron. Would have been the size of an old console record player - the kind that doubles as furniture.
Poor means hoping the toothache goes away.
Not really, there are open source FPGA cores for all kinds of things- though the Sparc is really the only heavy duty, real silicon open source processor.
Open source medical equipment is where the electronic designs, software, and diagnostic skills are completely and freely available to anyone who wants to build this piece of equipment for their own use. It will probably happen first in the developing world where this kind of equipment is not quite as illegal as it is sure to be in the West.
A lot of what passes for 'advanced' medical equipment in the US is actually kludged ancient technology. It sells for absurd amounts of money because of the bizarre 'cost-is-no-object' state of the American Health Care industry. And a lot of people are beginning to be denied basic medical care because they don't have the money to pay for it.
But a lot of medical tests could be done with inexpensive high-tech equipment that has been modified for home medical use. There may come an underground movement to build very high-tech medical equipment cheaply. Equipment that surpasses the quality of what is found in ordinary hospitals, but costs one tenth of the price. It would have no FDA certification, and would be quite illegal. No accredited doctor would use it.
The difference between open source software and open source medical equipment would be that the medical equipment would be illegal. And the people doing the test and interpreting the results would be subject to arrest for practicing medicine without a license.
But in many cases, the test results are just electronic data and can be analyzed by computer to give same level of professionalism as found in the hospital. An example of this would be having to pay $150 for a blood pressure test in a hospital that is identical to the test that you would get from the machine next to the door of your local grocery store.
The US electronic medical equipment industry is in about the same place as the US automobile industry was in early 1970's. Overly restricted by trivial regulations, smug in their belief in their omnipresent power, and completely unaware that they are about to get totally blindsided by people overseas who can do the job much cheaper and much better.
The USA lost the machine tools industry, the consumer electronics industry, most of the automobile industry, and many other industries by not paying attention to what the global consumers of these products actual need and want to buy. The US medical electronics industry is most likely being targetted now because it is showing all the same characteristics as those other industries that were dominated by American companies after World War Two.
"Some day, we will make our own TV, then our own TV shows, movies...
Then we are all set." -Andy Fong, on the Open-graphics mailing list.
Check out:
http://www.openhardwarefoundation.org/
http://www.opengraphics.org/
A lot of people are really taking this idea of open hardware designs very seriously, especially in graphics, where we have a really hard time getting docs out of GPU vendors to write Free Software drivers. One of the commenters on this article said something about how he and his colleagues who know how to do this stuff have no interest in doing it outside of work. This isn't true for everyone. The founder and leader of the Open Graphics Project is an experienced graphics chip designer.
You'll have to cross-compile a kernel, libc, a shell, some core utils and a compiler to the new architecture, thus you may unintentionally carry a hidden backdoor:
_ .22Trusting_Trust.22_backdoor_problem
http://en.wikipedia.org/wiki/Backdoor#The_classic
Unless you're also going to write your new free software from *absolute* scratch using *only* your new, open machine, you can not be 100% sure that you won't be controlled by any third party. That's going to be hard.
On the other side, theoretically all you need to bootstrap is a C compiler and its most basic dependencies, then you can compile the 'old' stuff like bash, Linux and GCC.
Rank the following tasks in order of complexity:
- gate-level design of a modern CPU
- gate-level design of a modern GPU
- gate-level design of a modern northbridge
- gate-level design of a modern southbridge
- gate-level design of a modern audio controller
- gate-level design of a modern ethernet controller
- gate-level design of a modern wifi chip
- gate-level design of a modern usb controller
- the linux kernel
my understanding is that there is a lot of really, really badly made hardware out there. the software people are clever enough to reverse engineer the hardware and write drivers. Why not put a few of them to work forward engineering the hardware?
Which peices of a modern computing system cannot run acceptably off of re-flashable firmware, or better yet, re-flashable FPGAs?
At this point, are (some) resources better spent trying to create F/OSS reference designs for every essential component to build a fully open computer platform?
I like the idea of being able to have a 100% open computer, where each of the components is well understood and discussed out in the open, and people aren't wasting a lot of time supporting badly made hardware. Some de-facto standardization around reference open source implementations of the hardware could be a pretty good thing.
It's actually not stuff like the CPU that i care about.. its more like.. all of the other things that make it onto a motherboard. There's no reason to put up with noisy audio, non-functional s/pdif outputs, buggy "hardware" raid, crappy bios, etc. The only value-add in these components is when they manage to live up to their as-advertised specs reliably.
My opinions are my own, and do not necessarily represent those of my employer.
I was almost worried we wouldn't see a FUD post by you in this thread. A thread on open source or Linux just isn't as good without a troll post by The_Abortionist.
Pad2Pad does less than they used to. The original idea of Pad2Pad was that they'd make the blank board, then assemble and solder all the parts, using anything in the Digi-Key catalog. That made it useful, especially since surface mount device soldering really needs to be done in a production environment with the right tooling.
But they couldn't do it profitably. Now they're just another blank PC board maker, of which there are hundreds. It's been routine to send out your board design files and get boards back for almost twenty years now.
How can you call anything that uses Flash as it's primary development tool open (in the FSF sense)?
I want a computer that I can trust, and one day I might not
be able to buy that from any of the major manufacturers.
As long as there are designs available, and places that can
make them, we will at least have options should the industry
giants do something stupid.
I can't wait until not just these, but also the production lines become opensource. I wait until we have open source models of mobile phones, cars, computers, airplanes, and their production lines open source as well!
http://id3as.livejournal.com/
OpenPOWER from IBM also.
Make SELinux enforcing again!
That's only true if the economic environment stays the same as it is today, especially with regards to cheap energy. The "peak oil" crowd claims that energy will get much more expensive in the future, in which case the existing economies of scale are lost and it becomes cost-effective to do more and more of the work yourself, or on a small, distributed, localized scale vs. huge and highly industrialized. Regardless of what you think of peak oil (I have serious doubts myself), it's just one of many possible ways in which the economic environment may change to make your assumptions untrue.
All of this disregards other potential factors, such as personal beliefs and preferences (maybe you want to avoid supporting certain corporations or business practices) or control (various cartels and special interests control the commercially-available hardware, making self-fabrication the only way to acquire certain types of hardware). This all may be hobbyist-level tinkering for now, but there's no telling when it might become very relevant.
Mind you, that was also a SPARC, albeit a SPARC clone. The ESA developed a fully GPLed rad-hardened SPARC replacement, which I believe Atmel then took over. But they were the first.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
"It's not that there is a lack of talent. Rather, apathy is fatal to open source. And we need to come to terms with the fact that the overwhelming majority of those with the knowledge to do something disruptive, to use their skill to change their world for the better, choose just to go home at night and watch tv."
Well I have the skill and talent however my education wasn't "open-source" and therefore I spend a lot of time at work paying for it, and when I get home the last thing I want to be bothered with is "my job".
I really like the license over at http://www.tapr.org/ohl.html it was created by a bunch of HAM radio guys.
To those of you saying "I have the skills, but why bother?" or "Why would some company bother?", I can give a halfway decent example of why "closed" hardware can kind of stink. Of course, its also an example of why "closed" hardware can kind of be nice, for the manufacturer, especially if they are also sell content for that hardware.
;)
I ported uClinux to the Sony PSP (check it out at http://df38.dot5hosting.com/~remember/chris/. It wasn't on slashdot because they had more important stories to run, like what operating systems the iPhone DOESN'T run. But I'm not bitter
Anyways, this project was a major pain in the ass, and at the moment its kind of stalled. The problem is that the hardware design is closed, and most of the components are all consolidated onto one giant Sony ASIC so inspecting the motherboard is no help.
So... It took a million years just to get the memory map right, and understand the exception/interrupt plumbing of this customized not-quite-MIPS-R4400 cpu core, and understand how to talk to the video, serialport, cache controller, etc.
Now, I happen to know at least 10 people who would buy a PSP if it had a really well supported linux. Allowing people to target a popular platform, rather than a proprietary one, would allow really neat applications that made use of this things built-in Wifi/Audio/etc. In short, if it was an open platform, it would allow for better interoperability, more diverse applications, blah blah blah. And if its Truly Truly "open", people could even make new PSP's that maintained compatibility with current PSP software, but optimized it for other tasks, etc. Whatever, you name it.
Of course, Sony is a content company. The memory stick interface, from which you can launch applications, makes one think "Maybe I can write some software to dump my friend's UMD game to memory stick, and then launch that game from the memory stick, so I can copy it." But thats REMARKABLY difficult on the PSP because they will only run memory stick code that is cryptographically signed by Sony (unless buffer overflow exploits are used, etc. which exist and are what make uClinux/PSP possible) and due to the closed nature of the platform, I don't think anyone even knows how to get a signed copy of a UMD onto a memory stick.
So it works pretty well for Sony. And it stinks for me.
"dont use it to make weapons, bla bla bla"
1 - Pansy ass. If it wasn't for those 'evil' weapons you wouldn't have the freedom to do your expirements.
2 - You released the 'specs', so you no longer get to choose how its used. So get over yourself.
Ya, mod me down, but that sort of 'clueless holier then now' attitude really pisses me off.
---- Booth was a patriot ----
I'm kinda hoping for someone to build a HDCP in => analog component, discrete audio out...
Someone should give a cheap implementation of SPARC a shot. IIRC, SPARC is very fast running C code because the way its internal registers are organized - minimizing memory hits to move stuff to and from a stack.
With the current critical mass of free and open-source software, there is little to no need to use x86 processors - a cheap, Solaris or Linux based notebook or desktop would solve a whole lot of problems people use those x86 abominations for.
My 166 MHz Ultra 1 still starts Firefox 2.5 faster than my 800MHz Pentium III. Other than the different processor architectures, I can't explain this difference (of course, the PC is running Windows, but not even that could explain the performance penalty).
http://www.dieblinkenlights.com
Okay, so the term "Open Source" gets stretched a lot these days, from "Open Source" religion to "Open Source" politics. In some places, it applies better than others. But IMHO, it is actually possible to share the "source code" by abstracting the hardware and sharing the info on-line. Think of it as a free and open inventory of hardware that anyone could access. Maybe "co-op hardware" is a better term for it. But still, the idea is that if we want to see a wider adoption of FOSS, we are going to have help people get it on hardware. And why not save the environment in the process? I started DIYparts.org, which is a free (beer and freedom) site for exchanging hardware locally, so as to avoid the cost of shipping. This is not really a shameless, plug, because it is there for the community to use. I don't make any money from the site.
1) SoC (MX.21)
2) Board-level design
3) OS (Linux (or probably ucLinux))
4) "Middleware" (Flash interpreter)
5) Applications
For Chumby, 2, 3 and 5 are open in some way or another. You don't have to write in Flash, it's just that they don't want you to distribute binary apps or anything that doesn't talk only to their network. Their ability to enforce this is hampered by US intellectual property law still having some limits though.
On a PC running Linux, the silicon RTL and board-level design and possibly some of the silicon programming details (video, wireless) aren't open, but people are still happy developing open windowing systems and open applications on it.
For one sense, the FSF uses the term "freedom" rather than "openness". For another, what is so non-free about haXe and Gnash?
It was about 1981 or 82 and my friend Stephen Hayes, then IIRC a Junior at Montclair Kimberley Academy in New Jersey, showed me assembler code he had written for the Apple ][. I had pored over Steve Wozniak's code which was distributed with my Apple ][ as well. Hayes' assembler didn't look like dot matrix printouts, he wrote and debugged it in pencil, a function to a sheet of paper. What he built that I remember:
/// and why I felt such loss when it got discontinued. The idea that you can do things that weren't expected is a great thing about open source. If anything, making it easier to write safe low-level code and add safely and cheaply add circuits with clip-on fpga based units would be fabulous for education. I only wish I still had my 5 1/4" floppy data! And I wish I could use the Apple P.I.E. (Programmers' Interactive Editor) for daily work.
A Robotron arcade game clone. Was just like the real thing. I think I worked on the splash screen maybe.
A monochrome high resolution, realtime 3D Asteroids game which I have never seen before or since then. Your isoceles tetrahedral spaceship can be aimed anywhere in 3D using two game paddles (a dial and button each) for altitude and azimuth. The asteroids are dodecahedrons and what have you, and everything (shooting, pulverizing of asteroids, etc.) happens in an oblong IIRC wraparound game space.
A polyphonic synthesizer (also in 6502 assembler like everything else). You could press and release several (up to 5 or 7 IRIC) keys on the keyboard simultaneously, individually and for arbitrary lengths of time, and the program generated *simultaneously voiced* complex chords by adding together the notes. This was mind-numbing. He wrapped it in tin foil and gave a concert to the school on the stage of the school auditorium. It was the Cars, a song which was going through my head the other day which is maybe why I remember now. At any rate nobody was expecting you could do something like this with an Apple ][.
Programming the Apple in Basic was fun, but Pascal (using the 16KB language card) and 6502 assembler were awesome. Pascal was the reason I loved my brother's later Apple
Open source governance was just an idea a few years ago. Now it is beginning. Not to put too fine of a point on it, but THAT is the way we will find true freedom.
To complete an open-source hardware project (say, design a complete computer) yourself, you would need an all-consuming geek passion.
But, if you work as part of a team with others, your contribution can be quite small, and the project can still have a large impact.
The idea is that you break up a project into small enough chunks that even those who don't have much time - say, only an hour a week - can contribute to a larger, exciting project.
For example, consider designing a computer motherboard. Think of the tasks that can be done independently:
- The power supply.
- The memory subsystem.
- The various busses and bus architecture.
- Various peripherals.
- The boot code and ROM/EPROM/EEPROM/FLASH programming.
- The CPU and memory architecture.
- The overall board schematic - partitioned among several people.
- The board layout.
One individual could do all of these, or the task could be split up among several people. Even those of us with packed schedules could manage to design the motherboard's power supply given a 6 month goal.I think the issue is that apathy is all too common. Yes, there are people interested in doing these things, but unfortunately, we are so few and far between that the social connections upon which these projects are contingent never get formed.
The society for a thought-free internet welcomes you.
Well, anarchy is *true* freedom. But it inevitably degrades into a system of government at some point.
There is no supported Windows version of gEDA.
Without installing gEDA, you can still run it on a M$-only box.
Boot to a Live CD that contains gEDA:
The Usenet Archive -- sci.electronics.cad (Stuart Brorson)
I'd be surprized if there wasn't also a Windoze built on Bittorrent.
gewg_
I am building a business based on Open Source Hardware: http://www.rowetel.com/blog/?p=14. Open hardware also has potential to help the developing world: http://www.nextbillion.net/blogs/2006/09/05/is-ope n-source-hardware-an-answer
- standard board form factor
- CPU (Arm9 or OpenSparc or anything would do here)
- FPGA for emulation, graphics, and/or support functions (might need two)
- Flash Memory to store Open Firmware and FPGA bitstream
- RAM sockets (30-pin SIMM sockets are probably free of patent issues
;-)
- USB interface (for mass storage)
- free FPGA development tools
- Serial or PS/2 mouse/keybord port
- Parallel port (seem retro now, but good for for external hardware hacking)
- Internal Expansion bus standard (not aware of open designs for busses here)
All of the above has to be free of patent encumberance, so USB might be a problem.The C-One reconfigurable computer is a good prototype of what's possible.
The biggest open source hardware contribution would be:
Once you decide you want a robot, you'll need a board with a processor. These are systems that have good documentation, and some even claim some degree of "openness" in publishing schematics and encouraging you to build your boards yourself.
- MIT's Gogoboard (PIC microcontroller based 30-40 to build plus PC board)
http://padthai.media.mit.edu:8080/cocoon/gogosite
/ home.xsp?lang=en
- CMU's $400 TerkBot (FPGA and ARM) http://www.terk.ri.cmu.edu/recipes/index.php
- (I'm sure Stanford has something here too - I just don't know what it is)
- ARM7 boards with Ethernet for around $100 - Aleph1 claims some openness, but their site is down
- FPGA 'education' boards for $100-$150 w/ VGA and PC features http://www.digilentinc.com/
(digilent has upgraded the S3 board with more features, including LCD) You get approximately what you pay for, but you don't have to worry about DRM or odd bootloaders with this hardware. In most cases you STILL need a traditional PC to download software to these. The gogoboard is a cousin to the MIT cricket - using a PIC microcontroller. It won't run Linux as you think about Linux.