Yep, cascading dependencies are exactly why I wanted to skip the Kinect driver!
:-)
I tried using the Fedora OpenNI packages but that was as much effort as I was
willing
to put into it, seeing as I don't have a Kinect.
I'll give the media_build a try.
Thanks for your help!
>________________________________
>From: Andy Walls <[email protected]>
>To: Greg Fruth <[email protected]>; User discussion about IVTV
><[email protected]>
>Sent: Wednesday, May 25, 2011 2:32 AM
>Subject: Re: [ivtv-users] HVR-1600 frontend initialization failed
>
>Yes media_tree is a whole kernel build; you likely don't want that.
>
>It is my understanding that the media_build pulls down a media_tree and tries
>to build only the v4l-dvb modules for your kernel version. I have no
>firsthand experience.
>
>Somewhere in the build area there should be a .config file that you can
>manually edit to inhibit the build of the kinect module.
>
>This cx18 change is unfortunately not a one module fix. You'll at least need,
>IIRC, a new cx18, tda8290, tda18271, and s5h1411 modules. Since there have
>been various updates to infrastructure, you'll also need modules that those
>depend on: tuner, v4l-common and likely others. Dependencies tend to
>snowball. :(
>
>
>
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
