For the record, I got the drivers compiled and installed but so far I've only 
gotten them partially
working. The device sometimes works (in SD mode IIRC) using dd if=/dev/video0 
but I'm still trying
to figure out what the symptoms are.

Anyway, FWIW here's what I had to do to get media_tree to build on stock Fedora 
14 kernel
2.6.35.13-91.fc14.x86_64:

     git clone git://linuxtv.org/media_build.git
     cd media_build 
     ./build.sh

build.sh will stop at the Kinect driver with compiler errors. Edit build.sh to 
comment out the following

lines, or build.sh will clobber any code edits you make below: (editing the 
.config file doesn't seem to
work)


     #run git pull git://linuxtv.org/media_build.git master
     #run make -C linux/ download
     #run make -C linux/ untar

Assuming you don't need the Kinect driver, comment out or use #ifdef to disable 
the following line in
media_build/linux/drivers/media/video/gspca/kinect.c:

     int gspca_debug = D_ERR | D_PROBE | D_CONF | D_STREAM | D_FRAM | D_PACK |
          D_USBI | D_USBO | D_V4L2;


Assuming you don't need the Samsung S5P/EXYNOS4 SoC series MIPI-CSI driver, edit
media_build/linux/drivers/media/video/s5p-fimc/mipi-csis.c to comment out the 
line:

     #include <plat/mipi_csis.h>


and use #ifdef to skip the contents of the functions s5pcsis_set_params, 
s5pcsis_probe, s5pcsis_suspend,
and s5pcsis_resume, as they seem to be using bits from that include that my 
system doesn't have. Then
build.sh will complete successfully.


The rest of the instructions worked as-is.



>>________________________________
>>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

Reply via email to