On Sunday 19 November 2006 13:44, Martin Dauskardt wrote:
> I could solve the problem doing two things (not sure, if both are
> necessary):
>
> ivtv-driver.c:
> forgive me, if it`s nonsense, but shouldn`t it be
>
> #ifdef CONFIG_VIDEO_SAA7127_MODULE
>       if (hw & IVTV_HW_SAA7127)
>               ivtv_request_module(itv, "saa7127");
> #endif
> #ifdef CONFIG_VIDEO_SAA717x_MODULE
>       if (hw & IVTV_HW_SAA717X)
>               ivtv_request_module(itv, "saa717x");
> #endif
> #ifdef CONFIG_VIDEO_UPD64031A_MODULE
>
>
> instead of
>
> #ifdef CONFIG_VIDEO_SAA7127_MODULE
>       if (hw & IVTV_HW_SAA7127)
>               ivtv_request_module(itv, "saa7127");
> #endif
>       if (hw & IVTV_HW_SAA717X)
>               ivtv_request_module(itv, "saa717x");
> #ifdef CONFIG_VIDEO_UPD64031A_MODULE

There is no CONFIG option yet for the saa717x (it's not in the kernel, 
it's part of ivtv). But the IVTV_HW_SAA717X flag shouldn't be on for 
you unless you have a Japanese or Russian card I don't know about.

> Second, I build my 2.6.18-kernel without any video/DVB modules,
> because I always compile the current v4l-dvb hg. So I dont want to
> compile it twice and have no entries for the above mentioned modules
> in my .config and therefore also not in my
> /usr/include/linux/autoconf.h
>
> Is this necessary? Or is it sufficient to have it in
> v4l-dvb-xxx/v4l/.config ? (I merge ivtv 0.8 in v4l-dvb hg, because
> using trunk still gives unresolved symbols for ivtv-fb.ko)

I think it is sufficient to have it in .config. But lately I'm testing 
with a standard 2.6.18 kernel, not with v4l-dvb, so I'm not entirely 
sure yet.

>
> So I added the modules in my kernel config, patched ivtv-driver.c and
> now everything works!

The ivtv-driver.c patch should really not be necessary as far as I can 
tell.

        Hans

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to