All of lore.kernel.org
 help / color / mirror / Atom feed
From: jordan <triplesquarednine@gmail.com>
To: Glenn Elliott <gelliott@cs.unc.edu>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: nvidia bug or RT bug?
Date: Tue, 5 Jun 2012 20:25:53 -0400	[thread overview]
Message-ID: <CAOcfFMySsO-TQ43FzPcbCiXSStGD5x+rM=7PuJqQT6+_L3ng9Q@mail.gmail.com> (raw)
In-Reply-To: <loom.20120606T015743-749@post.gmane.org>

> Here is a patch carried forward for 302.06.03 (the beta driver I
> downloaded with CUDA 5.0 preview a few weeks ago).  They were
> the same for the 270 driver.  This has worked for me; maybe it will
> work for you.

I've actually got 302.11 running, nicely. I haven't had the crash i
originally posted about it a while (that doesn't mean it was fixed
necessarily).

here is a link (pastebin) to the patch that i am using;

http://pastebin.com/CXWtt3E1

do you see any problems, or something that may be missing? (aside from
the MSI stuff?) I ask because i suppose it is possible that nvidia has
changed, added something and the patch that i use is for the 290.
series and i just adapted the pkguibld (build-script) to use the
latest version. So if you see any issues let me know, and i could
forward that information to the packager who is maintaining this
patch.

> I am a little uncertain about my removal of "NV_INIT_MUTEX(mutex)
> semaphore_init(mutex)".  I can't remember what my rational was.

I have no idea. ;)

cheerz

Jordan
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-06-06  0:25 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
2012-06-05 23:32 ` Glenn Elliott
2012-06-06  0:03   ` Glenn Elliott
2012-06-06  0:25     ` jordan [this message]

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='CAOcfFMySsO-TQ43FzPcbCiXSStGD5x+rM=7PuJqQT6+_L3ng9Q@mail.gmail.com' \
    --to=triplesquarednine@gmail.com \
    --cc=gelliott@cs.unc.edu \
    --cc=linux-rt-users@vger.kernel.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.