[Discuss] OSHWA perspective on Arduino Yun?

Mario Gómez mxgxw.alpha at gmail.com
Fri Mar 20 18:14:28 UTC 2015

A little bit on topic:

Do you think that the recent dispute over the Arduino Trademark between
Arduino LCC and Arduino SRL has something to do about this?

I mean... reading the news it appears to me that Arduino SRL is only
interesting about having the control of the Trademark and not necessary to
follow the OSHW philosophy.

As I understand Arduino SRL designed the YUN, and the Arduino SRL CEO
(Federico Musto) is behind Linino (the Linux distribution on the YUN).

As a distributor for Arduino this really smells very fishy, a couple of
weeks ago I received an email from Gianluca talking about that they are not
going to ship anymore from Europe, but when I asked for clarifications I
didn't received any answers.

+ Info:



On Wed, Feb 25, 2015 at 2:17 PM, Drew Fustini <pdp7pdp7 at gmail.com> wrote:

> On Wed, Feb 25, 2015 at 10:56 AM, Mario Gómez <mxgxw.alpha at gmail.com>
> wrote:
> > Option 2 use a GPS module that only gives NMEA strings that is
> esentially a
> > black-box that I solder to my PCB and use an external microcontroller to
> > process everything.
> >
> > I decided to choose #2 because even if it's more expensive it allows me
> to
> > release full documentation and even considering that I don't know any of
> the
> > internal workings of the GPS module that I'm using it doesn't prevent me
> or
> > anyone to alter/modify the design.
> I think you have identified a common problem, and I believe you took
> the correct route from an OSHW perspective.  I think of it like your
> project is OSHW if you have released the design files needed to modify
> and redistribute it.
> There will always be monolothic components used in your design and
> listed in your BOM.  I don't think it raises concerns when that
> monolithic component is fixed function like an ADC.  However, I think
> it makes us less comfortable when that component contains a processor
> running firmware.  Pretty much any RF module falls in this category.
> I think such modules are fair to use in an OSHW project as long as the
> module can be purchased in low quantity from distributors, has a
> documented interface (like NMEA strings over serial) and is listed in
> your project BOM.
> cheers,
> drew
> BTW, I liked your point in previous post that a NDA would violate the
> "5. Free redistribution" clause of the OSHW definition.
> _______________________________________________
> discuss mailing list
> discuss at lists.oshwa.org
> http://lists.oshwa.org/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oshwa.org/pipermail/discuss/attachments/20150320/05f41e6b/attachment-0001.html>

More information about the discuss mailing list