On Wed, Sep 15, 2010 at 11:59 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: > You're in luck. I fixed this last weekend. It turns out that the > /dev/videoX device is created too soon and the HAL daemon starts to use it > immediately causing some initialization to go wrong or something like > that. Moving the creation of /dev/videoX to the end fixed this issue. > > This bug has been there probably for a long time, but it is only triggered > if some other process opens the device node immediately.
The "HAL daemon opening devices immediately" problem a pretty common bug with bridges (especially for hybrid devices) and I've fixed it for the ones I've seen. I'm surprised we don't get reports of this more often. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
