On Sun, Mar 7, 2010 at 2:03 PM, Theodore Kilgore <kilgota@xxxxxxxxxxxxxxxxxxxxxx> wrote: > It seems that the problem is solved by a local re-compile of the kernel plus > its modules, using the original distro .config settings in order to do this. > What I suspect has happened is that there was a simultaneous minor upgrade > of gcc at the same time, and it is possible that this interfered. I would > further speculate that a similar problem happened with you, in your Debian > installation. > > Hoping that we have finally tracked this down. It's a good theory. However, when I did my "update", I had compiled the kernel, installed it, rebooted into it and then proceeded to grab a fresh v4l tree and go from there. There wern't any package updates or anything else involved between the kernel compile and v4l compile. (except for the reboot into 2.6.33 of course.) -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
