public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John K <johnk_dev@yahoo.com>
To: ECos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] eCos license documentation in final products
Date: Tue, 21 Jul 2015 16:53:00 -0000	[thread overview]
Message-ID: <1437497416.88153.YahooMailBasic@web141604.mail.bf1.yahoo.com> (raw)

Greetings,

I've been spending the better part of this morning reading about the eCos license and GPL trying to figure out what I need to mention in the documentation for my final product.

For example, suppose I'm making a consumer grade coffee pot that runs eCos. What text do I need to include in the documentation mentioning the use of eCos? Obviously a customer of a coffee pot could care less about what operating system is making their coffee.

Second example, suppose I make a WiFi module that runs eCos. Think of it as a wireless NIC that can be embedded in an IOT device. Then a company who makes window blinds buys my module so their customers can wirelessly control the window blinds. What do I need to provide to the company who is buying my module? Note that they are using my module as a finished "product" - they have no idea or no concern about the OS it's using. Similarly, what would they have to provide to their customers? Note that the end customer is essentially 2 steps removed from the OS - they could care less about which wireless module is embedded in the blinds let alone the OS.

Thanks in advance for the clarification!
John

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2015-07-21 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 16:53 John K [this message]
2015-09-03 13:50 ` Alex Schuilenburg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1437497416.88153.YahooMailBasic@web141604.mail.bf1.yahoo.com \
    --to=johnk_dev@yahoo.com \
    --cc=ecos-discuss@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).