All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: jordan <triplesquarednine@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: nvidia bug or RT bug?
Date: Tue, 08 May 2012 11:58:10 -0400	[thread overview]
Message-ID: <1336492690.14207.189.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CAOcfFMx1J05oxWaXxBMSaMiMc0SWDpD57C9OtzqXtvRrsQBORw@mail.gmail.com>

On Tue, 2012-05-08 at 11:46 -0400, jordan wrote:

> I understand why you don't care about nvidia,

Because it's a proprietary driver and I can't see some of the code nor
can I fix it.


>  but if it is a bug in RT

It's not a bug in RT. It's a bug in how nvidia interacts with RT. When I
said it was both, I meant that it wont break in vanilla kernel, but only
breaks when nvidia is used with RT. But that's because RT changes
things, and drivers must adapt to be part of RT.

> - should it not be fixed?

There's nothing to fix.


>  anyways, I will report it to nvidia once i
> get a chance to. it would nice if they addressed RT-related problems

That's up to nvidia to decide.

> in their driver being as some folks do require proper/good 3d
> acceleration / real performance / Opengl 4.2 which (obviously) Nouveau
> does not provide, nor is it anywhere near providing in the foreseeable
> future :\ (not that this is news to anyone who has used them both).
> 
> > Bring up the bug with the nvidia rt patch maintainer. That's about all
> > I'll say on this matter.
> 
> No problem. I know the author of the patch, anyway. I just wanted some
> verification, rather than just making my own assumptions.

Thanks,

-- Steve



  reply	other threads:[~2012-05-08 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  1:17 nvidia bug or RT bug? jordan
2012-05-08 15:15 ` Steven Rostedt
2012-05-08 15:46   ` jordan
2012-05-08 15:58     ` Steven Rostedt [this message]
2012-06-05 23:32 ` Glenn Elliott
2012-06-06  0:03   ` Glenn Elliott
2012-06-06  0:25     ` jordan

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=1336492690.14207.189.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=triplesquarednine@gmail.com \
    /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.