>
>
> Hans Verkuil wrote:
>> Hi all,
>>
>> It took a long time (over 5 months) but here is the first release
>> candidate for the redesigned and cleaned up ivtv-0.10.0 driver.
>>
>> This driver will work with kernels 2.6.18 and 2.6.19.
>>
>> It can be downloaded here:
>> http://dl.ivtvdriver.org/ivtv/unstable/ivtv-0.10.0rc1.tar.gz
>>
>> Note: while it has been tested pretty well it remains a release
>> candidate, so if you have a really stable production system you might
>> not want to use this driver when making important recordings.
>>
>> My request is if you can all start testing this release candidate. I am
>> very happy with it as it is much easier to extend and improve than the
>> older versions. It should also be a lot more stable.
>>
>> It is interesting to compare the 0.9.2 release with this 0.10.0rc1
>> release with regard to code size:
>>
>> 0.9.1: 19305 lines, 586420 bytes
>> 0.10.0rc1: 14073 lines, 447377 bytes
>>
>> That's a reduction of about 25%!
>>
>> Before you start testing you should first read the notes at the
>> beginning of the included README file. The most important one is that
>> you need to use the included cx2341x encoder firmware. And if you use
>> ivtvfb then you will need to add extra kernel modules and most likely
>> you will also need to add the ivtv-fb module option osd_compat=1.
>>
>> I'd appreciate it if any posts regarding this release candidate are
>> prefixed with [RC1] (as I did for this post).
>>
>> If all goes well, then I hope to make a final release in 1-2 weeks. My
>> intention is to release a ivtv-0.18.0 for kernel 2.6.18, 0.19.0 for
>> kernel 2.6.19 and a 0.20.0 for kernel 2.6.20. This keeps the numbering
>> nicely regular. There will probably also be a 0.21.0 for kernel 2.6.21,
>> but in all likelyhood ivtv will be merged into kernel 2.6.22.
>>
>> Enjoy!
>>
>>      Hans
>
> Ok, I have 2 variables, so I'm not sure which is causing the problem,
> but......
>
> I just recently (over the weekend) changed out my motherboard (Gigabyte
> GA-K8NSC-939) to a Gigabyte K8NS-Ultra-939 (Has additional SATA
> controller & additional enet port & IEEE-1394).  As part of the
> changeout, I also upgraded the CPU from an Opteron 144 to an X2 3800+.
>
> The other change I made last night was to install these 0.10.0rc1 drivers.

What application are you using? MythTV? vdr? Just plain 'cat'?

       Hans

>
>
> Somewhere along the way, I am now getting TONS of these:
>
> I remember now that I was getting these using 0.8.1 drivers on my
> Opteron 144, but I got around it by adding the option: mpg_buffers=16
> but apparently that isn't valid for the new 0.10 drivers, because ivtv
> wouldn't load.
>
> Any further hints/clues as to what is going on and how to fix, outside
> of custom hacking/building the driver module as outlined in this thread:
> http://www.gossamer-threads.com/lists/ivtv/devel/33976
>
>
> ivtv0: All encoder VBI stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder MPEG stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder VBI stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder VBI stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder MPEG stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder MPEG stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder VBI stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder MPEG stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
> ivtv0: All encoder VBI stream buffers are full. Dropping data.
> ivtv0: Cause: the application is not reading fast enough.
>
>
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  ==================== START INIT
> IVTV ====================
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  version 0.10.0 (tagged release
> candidate#1) loading
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  Linux version: 2.6.18-2-k7 SMP
> mod_unload K7 REGPARM gcc-3.3
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  In case of problems please
> include the debug info between
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  the START INIT IVTV and END INIT
> IVTV lines, along with
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  any module options, when mailing
> the ivtv-users mailinglist.
> Feb  5 23:25:22 mythtv1 kernel: pci_hotplug: PCI Hot Plug PCI Core
> version: 0.5
> Feb  5 23:25:22 mythtv1 kernel: intel8x0_measure_ac97_clock: measured
> 59862 usecs
> Feb  5 23:25:22 mythtv1 kernel: intel8x0: clocking to 46976
> Feb  5 23:25:22 mythtv1 kernel: agpgart: Detected AGP bridge 0
> Feb  5 23:25:22 mythtv1 kernel: agpgart: Setting up Nforce3 AGP.
> Feb  5 23:25:22 mythtv1 kernel: agpgart: AGP aperture is 32M @ 0xf0000000
> Feb  5 23:25:22 mythtv1 kernel: i2c_adapter i2c-0: nForce2 SMBus adapter
> at 0x1c00
> Feb  5 23:25:22 mythtv1 kernel: i2c_adapter i2c-1: nForce2 SMBus adapter
> at 0x2000
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Autodetected Hauppauge card
> (cx23416 based)
> Feb  5 23:25:22 mythtv1 kernel: ACPI: PCI Interrupt 0000:02:07.0[A] ->
> Link [APC4] -> GSI 19 (level, low) -> IRQ 177
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Unreasonably low latency timer,
> setting to 64 (was 32)
> Feb  5 23:25:22 mythtv1 kernel: logips2pp: Detected unknown logitech
> mouse model 77
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: loaded v4l-cx2341x-enc.fw
> firmware (376836 bytes)
> Feb  5 23:25:22 mythtv1 kernel: input: ImExPS/2 Logitech Explorer Mouse
> as /class/input/input2
> Feb  5 23:25:22 mythtv1 kernel: ts: Compaq touchscreen protocol output
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Encoder revision: 0x02060039
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 2-0050: Hauppauge model 32032,
> rev B310, serial# 7045282
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 2-0050: tuner model is Philips
> FI1236 MK2 (idx 10, type 2)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 2-0050: TV standards NTSC(M)
> (eeprom 0x08)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 2-0050: audio processor is
> MSP4448 (idx 27)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 2-0050: decoder processor is
> SAA7115 (idx 19)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 2-0050: has no radio, has IR
> remote
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Autodetected Hauppauge WinTV
> PVR-250
> Feb  5 23:25:22 mythtv1 kernel: tuner 2-0061: chip found @ 0xc2 (ivtv
> i2c driver #0)
> Feb  5 23:25:22 mythtv1 kernel: saa7115 2-0021: saa7115 found @ 0x42
> (ivtv i2c driver #0)
> Feb  5 23:25:22 mythtv1 kernel: msp3400 2-0040: MSP4448G-A2 found @ 0x80
> (ivtv i2c driver #0)
> Feb  5 23:25:22 mythtv1 kernel: msp3400 2-0040: MSP4448G-A2 supports
> radio, mode is autodetect and autoselect
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Registered device video0 for
> encoder MPEG (4 MB)
> Feb  5 23:25:22 mythtv1 kernel: msp3400 2-0040: MSP4448G-A2 supports
> radio, mode is autodetect and autoselect
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Registered device video0 for
> encoder MPEG (4 MB)
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Registered device video32 for
> encoder YUV (2 MB)
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Registered device vbi0 for
> encoder VBI (1 MB)
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Registered device video24 for
> encoder PCM audio (1 MB)
> Feb  5 23:25:22 mythtv1 kernel: tuner 2-0061: type set to 2 (Philips
> NTSC (FI1236,FM1236 and compatibles))
> Feb  5 23:25:22 mythtv1 kernel: ivtv0: Initialized Hauppauge WinTV
> PVR-250, card #0
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  ======================  NEXT CARD
>   ======================
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Autodetected Hauppauge card
> (cx23416 based)
> Feb  5 23:25:22 mythtv1 kernel: ACPI: PCI Interrupt 0000:02:09.0[A] ->
> Link [APC2] -> GSI 17 (level, low) -> IRQ 185
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Unreasonably low latency timer,
> setting to 64 (was 32)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: loaded v4l-cx2341x-enc.fw
> firmware (376836 bytes)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Encoder revision: 0x02060039
> Feb  5 23:25:22 mythtv1 kernel: tuner 3-0061: chip found @ 0xc2 (ivtv
> i2c driver #1)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 3-0050: Hauppauge model 26582,
> rev F0B2, serial# 9709741
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 3-0050: tuner model is TCL
> M2523_5N_E (idx 112, type 50)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 3-0050: TV standards NTSC(M)
> (eeprom 0x08)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 3-0050: audio processor is
> CX25843 (idx 37)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 3-0050: decoder processor is
> CX25843 (idx 30)
> Feb  5 23:25:22 mythtv1 kernel: tveeprom 3-0050: has no radio, has no IR
> remote
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Autodetected Hauppauge WinTV
> PVR-150
> Feb  5 23:25:22 mythtv1 kernel: cx25840 3-0044: cx25843-23 found @ 0x88
> (ivtv i2c driver #1)
> Feb  5 23:25:22 mythtv1 kernel: cx25840 3-0044: loaded v4l-cx25840.fw
> firmware (16382 bytes)
> Feb  5 23:25:22 mythtv1 kernel: wm8775 3-001b: chip found @ 0x36 (ivtv
> i2c driver #1)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Registered device video1 for
> encoder MPEG (4 MB)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Registered device video33 for
> encoder YUV (2 MB)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Registered device vbi1 for
> encoder VBI (1 MB)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Registered device video25 for
> encoder PCM audio (1 MB)
> Feb  5 23:25:22 mythtv1 kernel: tuner 3-0061: type set to 50 (TCL 2002N)
> Feb  5 23:25:22 mythtv1 kernel: ivtv1: Initialized Hauppauge WinTV
> PVR-150, card #1
> Feb  5 23:25:22 mythtv1 kernel: ivtv:  ====================  END INIT
> IVTV  ====================
>
>
> --
> Mark Paulus
> 2424 Garden of the Gods Rd  | Phone:  v622-5578 / 719-535-5578
> 0419/117 - LEC Access ; D5-1010   | FAX:    719-535-1665
> Colo Springs, CO  80919    | 1800PageMCI / 1406052
> AIM : mgpaulus1    /  sametime : mark.paulus
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users



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

Reply via email to