FOSDEM lightning talk slides was[Re: FOSDEM]

Ron K. Jeffries rjeffries at
Thu Feb 4 11:53:57 EST 2010

Copyleft hardware includes (to my mind) open hardware
projects which incorporate complex silicon such as a processor
where the programming API is open, but the chip manufacturer
does not disclose detailed design at gate level.

Arduino is a good example, where multiple outfits around the
world design, manufacture and sell PCBs and kits that are
clones of Arduino, or are "shields" that plug in and add functions.

Copyleft SILICON such as MilkyMist takes openess to the gate

If we believe that only the gate level Copyleft approach is valid,
it excludes a universe of open hardware projects that can
be both beneficial and FUN.

I do NOT oppose the more radical gate level copyleft,
but to my mind it is a future goal, not something with
broad practical application for a LONG time.

Reasonable people may reasonably disagree.

Ron K. Jeffries

On Thu, Feb 4, 2010 at 07:24, Sébastien Bourdeauducq
<sebastien.bourdeauducq at> wrote:
> On Thursday 04 February 2010 13:58:47 Jon Phillips wrote:
>> dudes, I started a page for our presentations at FOSDEM. Please add to
> it
>> with abstracts, etc.
> "Drawing on examples from Shanzai Hardware from China, Arduino"
>                                                      ^^^^^^^
> Arduino is no good example of open hardware. It's just yet another
> microcontroller evaluation board with available schematics and gerber
> files. Such boards with the same availability of data have existed since
> microcontrollers were invented, and manufacturers do not give a damn if
> you copy them (it just makes them sell more chips!).
> Regarding hardware, the only thing they got open-source-ish is the
> community; all claims about technical openness are bullshit. The
> proprietary AVR chip does EVERYTHING, and any competent person can design
> all the rest in a mere hour or two.
> Sébastien
> _______________________________________________
> Qi Developer Mailing List
> Mail to list (members only): developer at
> Subscribe or Unsubscribe:

More information about the discussion mailing list