I just tried V4L2 on RH7.1 for the first time yesterday, so sorry if I haven't got the following right yet. I think what causes the make to say that modules are not enabled is because the Makefile is using the .config file for that information. Out of the box, there is no .config file in the Linux source directory. Copy one from the configs subdirectory to the main Linux source directory as .config. The videodevX-make depends on the kernel config so that the resulting module will be compatible with the kernel. The kernel compile process creates header files from the configuration data that modules depend on to be compiled right. You wouldn't want to load a uniprocessor (the default) compiled module into an SMP kernel, for example. The necessary files for the videodevX make just aren't there on an out-of-box RH install. The version information on module symbols option is causing compile errors with Red Hat's compiler in 7.1. Needs to be turned off in the kernel config. I noticed compile errors from the V4L2 videodev.h in some v4l drivers. The V4L2 videodev.h needs to be fixed to be compatible. In the mean time turn off v4l drivers you don't need in the kernel config. Bill. "Darragh O Flanagan (EEI)" wrote: > > Recompiling the kernel and modules seems to work. > > I managed to get v4l2 working nicely. > > However since I planning on writing a detailed set of instructions for all of this, I was wondering... > > Alan Cox wrote: > > Out of the box RH 7.1 has kernel modules enabled. That bit I can assure you > > If this is the case then why doesn't videodevX detect this and install correctly without having to recompile everything? > > am I missing the point?
