man, 08,.11.2004 kl. 20.55 +0100, skrev Damien Sandras: > It is most probably a driver bug. I don't think adding a workaround for > a driver problem in GnomeMeeting is a good idea. The problem needs to be > fixed at its root, not as a workaround in the client. Actually I agree in principle. Unfortunately I had an email-discussion last week with the author of the kernel-driver which led nowhere. It seems like we either have to live with this bug or use the 0_NONBLOCK-flag on ::open and handle a return-value of -EWOULDBLOCK when the device is busy. This is specific for this driver and (as far as I can see) not a part of the standard V4L2-API. I volunteered to create a patch which uses the standard way and return -EBUSY, but he never answered that part of my mails. Right now I've got to much other stuff on my hands so I'll let Nicola or someone else try to fix this with him :) -- Cheers, Heikki
Attachment:
signature.asc
Description: Dette er en digitalt signert meldingsdel