From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ng Oon-Ee <ngoonee@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Nvidia patches for 2.6.33-rt?
Date: Thu, 4 Mar 2010 09:42:17 +0100 [thread overview]
Message-ID: <20100304084217.GC5011@pengutronix.de> (raw)
In-Reply-To: <4ccf65461003031920x4384ab8cg2b89ba890009ea8f@mail.gmail.com>
> > I have absolutely no idea if this is the best way to handle the semaphore_init
> > issue, I don't even know what a semaphore is, but I submitted a simple patch at
> > http://www.nvnews.net/vbulletin/showthread.php?t=148509 anyway. It builds and
> > appears to be working, but I'd like some verification that sema_init(mutex,1) is
> > a valid substitute for semaphore_init(mutex).
> >
> > --
> > 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
> >
>
> Works here as well (for nvidia 195.36.08). Many thanks, Jonathan. Such
> a simple patch compared to the previous one for 2.6.31-rt.
The patch is much easier now because the spinlock functions are
nicely wrapped in NV_... macros in nvidia's patch.
> Would still appreciate information from someone who knows the code
> about sema_init(mutex,1) though =).
Well, it should work the same. Still I wouldn't be surprised if this
should be a mutex instead, I havn't looked.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
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
prev parent reply other threads:[~2010-03-04 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 8:59 Nvidia patches for 2.6.33-rt? Ng Oon-Ee
2010-03-02 9:16 ` Xavier Miller
2010-03-02 9:47 ` Tim Blechmann
2010-03-03 12:16 ` Jonathan Schmidt
2010-03-04 3:20 ` Ng Oon-Ee
2010-03-04 8:42 ` Uwe Kleine-König [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=20100304084217.GC5011@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=ngoonee@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 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 NNTP newsgroup(s).