On Thu, 2008-09-18 at 20:17 -0500, Mr cctsurf wrote: > I am, however, running into an insertion problem now... I'm afraid their > connected > the following is my dmesg: > > Linux video capture interface: v2.00
> cx18-0: Unreasonably low latency timer, setting to 64 (was 32) > cx18-0: cx23418 revision 01010000 (B) > tveeprom 2-0050: Huh, no eeprom present (err=-121)? > tveeprom 2-0050: Encountered bad packet header [01]. Corrupt or not a > Hauppauge eeprom. > cx18-0: Invalid EEPROM > DVB: registering new adapter (cx18) > s5h1409_readreg: readreg error (ret == -121) > cx18-0: frontend initialization failed > cx18-0: DVB failed to register You appear to be running into the problem where the CX23418 is responding properly to back-to-back accesses to different regions of the CX23418. You should attempt to load the cx18 module with it's mmio_ndelay option set to some multiple of 30.3 ns: 31, 61, 91, 121, 152, or some other multiple, until EEPROM recognition and other I2C operations work properly (no -121 -EREMOTEIO errors). If you can't things to work doing that, we can try some other things later, like: a. use longer delays to reset chips on the card b. set the secondary latency timer of the bridge the CX23418 is behind a little longer > cx18-0: Registered device video2 for encoder YUV (2 MB) > cx18-0: Registered device video3 for encoder PCM audio (1 MB) > cx18-0: Registered device radio0 for encoder radio > cx18-0: Error -12 registering devices > tda9887 3-0043: destroying instance > cx18-0: Error -12 on initialization > cx18: probe of 0000:00:0a.0 failed with error -12 > cx18: End initialization -12 is -ENOMEM: you ran out of memory for allocating buffers. To address this you have a few things to try: 1. Add a 'vmalloc=xxxM' to your kernel command line that is 128M greater than what /proc/meminfo currently shows for your VmallocTotal. The CX23418 consumes a contiguous 64 MB chunk of address space, and may leave you low on vmalloc addresses (esp. on 32 bit kernels). 2. Set the enc_yuv_buffers, enc_vbi_buffers, enc_pcm_buffers module parameters to 0 and the enc_mpg_buffers to 1 MB instead of the default of 2 MB. This is just a work around, until you can figure out how to get more dynamically allocated memory available on your system available to the cx18 driver. > I hope it's not false hope, I'm also interested if there is a git checkout > known to work. > In retrospect, I don't think it's a headers change issue, because I never > changed them on this computer until now. It should not be that, AFAICT. Regards, Andy > Thanks, > cctsurf _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
