All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Webb <jeff.webb@nta-inc.net>
To: 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 17:18:48 -0600	[thread overview]
Message-ID: <5488D4D8.7010604@nta-inc.net> (raw)
In-Reply-To: <20141210220129.GP24110@csclub.uwaterloo.ca>

On 12/10/2014 04:01 PM, Lennart Sorensen wrote:
> On Wed, Dec 10, 2014 at 03:55:21PM -0600, Jeff Webb wrote:
>> I can confirm that this is around the time I started having trouble with the proprietary nvidia module.  In the linux 2.6.?? days, I didn't experience that issue.  It is obviously up to the authors to decide whether or not it is desirable to allow proprietary modules to continue to operate on an I-pipe patched kernel as they do an un-patched kernel.  Since the issue was raised, I thought I would report my experience in case there is a desire to get this configuration working again.
>
> Well certainly I do agree with Gilles that if there is a binary blob,
> you can not know if it is going to mess directly with interrupts and
> break ipipe, so the nvidia driver could be a problem (hard to know).

Yes, this is true.  Just to be clear, though, I have used Xenomai with the nvidia module loaded, and it does work well enough to be useful for some applications on some hardware.  I would not recommend this configuration for a critical application, but it may be useful to some people for development and testing.  The open-source nouveau driver is much better behaved, but some video cards don't work well with nouveau.

-Jeff



  reply	other threads:[~2014-12-10 23:18 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
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 [this message]
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=5488D4D8.7010604@nta-inc.net \
    --to=jeff.webb@nta-inc.net \
    --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.