From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code
Date: Wed, 10 Dec 2014 20:57:49 +0100 [thread overview]
Message-ID: <20141210195749.GX1524@hermes.click-hack.org> (raw)
In-Reply-To: <20141210195236.GI24110@csclub.uwaterloo.ca>
On Wed, Dec 10, 2014 at 02:52:36PM -0500, Lennart Sorensen wrote:
> On Wed, Dec 10, 2014 at 08:44:58PM +0100, Gilles Chanteperdrix wrote:
> > And by the way, you are not "reverting a change". The I-pipe
> > starting with the version for Linux 3.2 was rewritten from scratch
> > and called "I-pipe core", did not you see the file names changing ?
> > So, what you have may simply have been a mistake. Or maybe not.
>
> I never realized changing ipipe to ipipe core was a huge change, and
> certainly never noticed it was a rewrite. It seemed to work about the
> same with xenomai.
>
> > And if you want to talk about stupid, using proprietary modules in
> > products based on Xenomai you redistribute is really stupidly
> > dangerous, both technically and legally.
>
> Well to manage T1/E1 ports that was what existed.
>
> I don't see a technical problem, we have the sources and are compiling
> from source. The modules build and work fine on the kernel without ipipe,
> so clearly it isn't using any part of ipipe.
The technical problem is that the I-pipe relies on macro to
substitute local_irq_save and local_irq_restore in all the code
running in the linux kernel. So technically, any code which uses
local_irq_save and local_irq_restore uses the I-pipe, in an I-pipe
patched kernel. If any code runs which disables the irqs without
using these macros, because it is shipped pre-compiled, then you may
just have lost real-time guarantees.
--
Gilles.
next prev parent reply other threads:[~2014-12-10 19:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 18:37 [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code Lennart Sorensen
2014-12-10 18:42 ` Gilles Chanteperdrix
2014-12-10 19:02 ` Lennart Sorensen
2014-12-10 19:04 ` Lennart Sorensen
2014-12-10 19:05 ` Gilles Chanteperdrix
2014-12-10 19:09 ` Lennart Sorensen
2014-12-10 19:11 ` Lennart Sorensen
2014-12-10 19:12 ` Gilles Chanteperdrix
2014-12-10 19:13 ` Gilles Chanteperdrix
2014-12-10 19:19 ` Lennart Sorensen
2014-12-10 19:24 ` Gilles Chanteperdrix
2014-12-10 19:39 ` Lennart Sorensen
2014-12-10 19:47 ` Gilles Chanteperdrix
2014-12-10 19:55 ` Lennart Sorensen
2014-12-10 19:59 ` Gilles Chanteperdrix
2014-12-10 20:05 ` Lennart Sorensen
2014-12-10 19:44 ` Gilles Chanteperdrix
2014-12-10 19:52 ` Lennart Sorensen
2014-12-10 19:57 ` Gilles Chanteperdrix [this message]
2014-12-10 20:12 ` Lennart Sorensen
2014-12-10 19:45 ` Philippe Gerum
2014-12-10 19:44 ` Lennart Sorensen
2014-12-10 20:13 ` Philippe Gerum
2014-12-10 20:11 ` Lennart Sorensen
2014-12-10 20:38 ` Philippe Gerum
2014-12-10 21:16 ` Lennart Sorensen
2014-12-10 21:23 ` Lennart Sorensen
2014-12-10 21:55 ` Jeff Webb
2014-12-10 22:01 ` Lennart Sorensen
2014-12-10 23:18 ` Jeff Webb
2014-12-10 20:53 ` Jeff Webb
2014-12-10 21:58 ` Gilles Chanteperdrix
2014-12-22 10:06 ` Jan Kiszka
2014-12-22 11:19 ` Philippe Gerum
2014-12-22 14:46 ` Lennart Sorensen
2014-12-22 15:00 ` Philippe Gerum
2014-12-22 19:08 ` Lennart Sorensen
2014-12-22 14:42 ` Lennart Sorensen
2014-12-22 14:44 ` Jan Kiszka
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=20141210195749.GX1524@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.