But that's not much of an argument here, because any solution will require
patching libng or even its v4l2 driver.
Anyway, by doing it Youness' way we will avoid an ugly thing like if(driver ==
pwc) { . } by adding a real feature. The only disadvantage being all
reports about 'webcam not
Hi,
for me the better solution is to find the bug and eliminate it
Phil
P.S. I don't have marks anymore only curses, so I consider I am almost in
holidays !
Le Monday 12 June 2006 18:17, Harry Vennik a écrit :
But that's not much of an argument here, because any solution will require
Why not contacting Luc Saillard to inform him of the bug ?
Phil
Le Monday 12 June 2006 18:40, Harry Vennik a écrit :
I think it simply isn't an amsn bug, but a driver bug.
The streaming support on pwc seems to be somewhat buggy.
That is why clearing the V4L2_CAP_STREAMING capability flag will
So what does upstream say about this bug?
On Mon, 2006-06-12 at 18:40 +0200, Harry Vennik wrote:
I think it simply isn't an amsn bug, but a driver bug.
The streaming support on pwc seems to be somewhat buggy.
That is why clearing the V4L2_CAP_STREAMING capability flag will make it work.
On
of course that's a good thing to do, but it won't fix it for users with an
older pwc, and we cannot assume all users will upgrade. some might even not
know how to do it, or not have root access to the system.
Op maandag 12 juni 2006 18:49, schreef Philippe Valembois - Phil:
Why not contacting
but we can still say: go update or don't bother us. Anyway it is
important to let upstream know about this
On Mon, 2006-06-12 at 19:16 +0200, Harry Vennik wrote:
of course that's a good thing to do, but it won't fix it for users with an
older pwc, and we cannot assume all users will upgrade.
not only that, but we'd need to shift the responsability... we really
should stop being so nice to the users, look at what happened lately in
the forums because of AA fonts and tcl/tk 8.5... he was a stupid bastard
but let's take his example
why bother if the problem isn't ours ? If
A buggy driver is not our fault, that is very clear. But if we know a
work-around, we MAY use that to make things easier for our users. Of course
we should not spend 3 days of programming to work around a bug that is not
our fault, but a 10-minute fix is okay. And where the line is in between,
