Re: [GnomeMeeting-devel-list] V4L2 device detection patch



Who is the driver author? Luca?
I should be able to discuss that with him.

But I can not add a different workaround in GnomeMeeting for every
different bug of every camera driver...


Le lundi 08 novembre 2004 à 21:20 +0100, Heikki Henriksen a écrit :
> 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 :)
> 
> _______________________________________________
> Gnomemeeting-devel-list mailing list
> Gnomemeeting-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
-- 
 _      Damien Sandras
(o-     GnomeMeeting: http://www.gnomemeeting.org/
//\     FOSDEM      : http://www.fosdem.org
v_/_    H.323 phone : callto:ils.seconix.com/dsandras seconix com





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]