> > 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@xxxxxxxxxxxxxxx > > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
