public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Klaas Gadeyne <klaas.gadeyne@fmtc.be>
Cc: Andrew Lunn <andrew@lunn.ch>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Project ideas for graduate course
Date: Wed, 01 Aug 2007 12:31:00 -0000	[thread overview]
Message-ID: <20070801123053.GC31277@lunn.ch> (raw)
In-Reply-To: <Pine.LNX.4.64.0708011359211.3918@ampere.labo01.fmtc.be>

> Even _without_ all the license issues that would be a good thing.
> However, when we first implemented EML, the EtherCAT people were still
> working on conformance testing.

Is that now finished? Is it time for version 0.2 of the code with
extra conformance testing?

> Also note that the extra clause is an agreement between Beckhoff and
> the licensee (and FMTC has nothing to do with that agreement), that
> "protects" the licensee from patent claims covering the EtherCAT
> technology.

Maybe GPLv3 is the solution. That includes patent protection as far as
i understand. 

  Andrew

-- 
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:[~2007-08-01 12:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 13:36 Rohit
2007-07-30 17:26 ` Mike Arthur
2007-07-31  7:34   ` Rohit
2007-07-31  9:35     ` Andrew Lunn
2007-07-31  9:50       ` Klaas Gadeyne
2007-07-31 10:01         ` Andrew Lunn
2007-07-31 11:17           ` Klaas Gadeyne
2007-07-31 12:12             ` Andrew Lunn
2007-07-31 12:36               ` Klaas Gadeyne
2007-07-31 13:01                 ` Andrew Lunn
2007-08-01  8:04                   ` Klaas Gadeyne
2007-08-01 10:09                     ` Andrew Lunn
2007-08-01 12:14                       ` Klaas Gadeyne
2007-08-01 12:31                         ` Andrew Lunn [this message]
2007-08-02 11:39                           ` Klaas Gadeyne
2007-07-31 14:31               ` [ECOS] " Grant Edwards

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=20070801123053.GC31277@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=klaas.gadeyne@fmtc.be \
    /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).