Why We Need Free Digital Hardware Designs

jrepin writes Free software is a matter of freedom, not price; broadly speaking, it means that users are free to use the software and to copy and redistribute the software, with or without changes. Applying the same concept directly to hardware, free hardware means hardware that you are free to use and to copy and redistribute with or without changes. But, since there are no copiers for hardware, is the concept of free hardware even possible? The concept we really need is that of a free hardware design. That's simple: it means a design that permits users to use the design (i.e., fabricate hardware from it) and to copy and redistribute it, with or without changes. The design must provide the same four freedoms that define free software. Then "free hardware" means hardware with an available free design.

Comments

opencores.org

[pem]

There are a lot of free designs and sites supporting them out there. Open source hardware is a thing. Even "free" (according to RMS) hardware is a thing.

Is there some new point to this?

Re:opencores.org

[ShanghaiBill]

There are a lot of free designs and sites supporting them out there.

My favorite is opencores.org. They have a lot of free hardware IP, many using the standard Wishbone bus. The cores can be used in an FPGA, or incorporated into an ASIC. It is a fantastic resource.

Tools for modifying open hardware designs

[Change]

OSHW has a bit of a difficulty associated with it, and that's the tools used to view/edit the designs. Many proprietary PCB CAD packages are offered in free-as-in-beer versions for boards up to a certain size or pin count, but then you're locked into that package. If you want to take that design and expand it beyond those constraints then you're stuck buying into the next step up of the software, or you have to fully re-design (schematic capture and layout) in another tool. Fortunately KiCAD (http://www.kicad-pcb.org/) seems to be picking up a bit of steam, but for those already using other tools, unless they're deep believers in the full open toolchain philosophy, what incentive do they have to switch packages (and re-implement their existing designs in that new package)?

Re:Tools for modifying open hardware designs

[dbc]

Sorry to tell you, but you and I are about the only two people in the world to believe this. I use gEDA, BTW, which is another free-as-in-speech alternative to KiCAD, and much older. So far, I have been very frustrated trying to make the case that open hardware designs need to be "elephants all the way down" -- FOSS from the hardware design, to the DA tools (and file formats and libraries), to the OS. In fact, I once had a several-post-long exchange with Limor Fried over at AdaFruit's forums where she finally closed off the thread with: "Tools don't matter." I think her opinion is outrageously misguided and short-sighted, but that is an example of what the leaders of the Open Hardware community are thinking. SparkFun must feel the same way, because all of their designs are released on cripple-ware tools, too.

I think we need an open hardware license that includes a clause about openly documented file formats at the very least, and I would push for a license that calls for design files released on open source DA tools. Imagine where the Linux ecosystem would be today without gcc. Gcc isn't a great compiler, but it is open source, and it got us where we are today.