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
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.
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.
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.
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.
Ronja
The schematics for electronics and mechanical design are available, including in enditable source form.
SJW n. One who posts facts.
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 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."
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.
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.
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.