Replying to myself:

After playing with things for a while, I've noticed that the sound seems
a bit high-pitched and it seems to skip every second or so in mythtv
(this doesn't start happening, apparently, until after I run
mythfrontend the first time).

This even seems to happen when just copying from /dev/video0
to /dev/video16

(prior to running mythfrontend, everything seems to be fine)

my ivtv dmesg output during module loading looks like:

ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.10.0 (tagged release) loading
ivtv:  Linux version: 2.6.19-1.2911.fc6 mod_unload 
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge card (cx23415 based)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02060039
ivtv0: Decoder revision: 0x02020023
tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver
#0)
saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
msp3400 0-0040: MSP4448G-A2 supports radio, mode is autodetect and
autoselect
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
lirc_dev: lirc_register_plugin: sample_rate: 10
tveeprom 0-0050: Hauppauge model 48132, rev K268, serial# 9904748
tveeprom 0-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is MSP4448 (idx 27)
tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
tveeprom 0-0050: has radio, has IR remote
ivtv0: Autodetected Hauppauge WinTV PVR-350
ivtv0: Registered device video0 for encoder MPEG (4 MB)
ivtv0: Registered device video32 for encoder YUV (2 MB)
ivtv0: Registered device vbi0 for encoder VBI (1 MB)
ivtv0: Registered device video24 for encoder PCM audio (1 MB)
ivtv0: Registered device radio0 for encoder radio
ivtv0: Registered device video16 for decoder MPEG (1 MB)
ivtv0: Registered device vbi8 for decoder VBI (1 MB)
ivtv0: Registered device vbi16 for decoder VOUT
ivtv0: Registered device video48 for decoder YUV (1 MB)
ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
tuner 0-0061: type set to 47 (LG NTSC (TAPE series))
ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
ivtv:  ====================  END INIT IVTV  ====================


and after loading the ivtv-fb module I get:

ivtv0-fb: Framebuffer at 0x85510000, mapped to 0xd7110000, size 1665k
ivtv0-fb: === Validated display mode  ===
ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
ivtv0-fb: Display position 1,1
ivtv0-fb: Display filter : on
ivtv0-fb: Color space : RGB
ivtv0-fb: === Display mode change ===
ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
ivtv0-fb: Display position 1,1
ivtv0-fb: Display filter : on
ivtv0-fb: Color space : RGB
ivtv0-fb: Running in compatibility mode. Display resize & mode change
disabled
ivtv0-fb: Framebuffer registered on ivtv card id 0


The cpu load is low (around 3-4% when doing cat /dev/video0
> /dev/video16).  

My xorg.conf looks like:


Section "ServerLayout"
        Identifier     "Default Layout"
        Screen      0  "TV" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "ServerLayout"
        Identifier     "ATI-Layout"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
EndSection

Section "Device"
        Identifier "Hauppauge PVR 350 Framebuffer"
        Driver "ivtvdev"
        Option  "fbdev" "/dev/fb1"
        Option  "ivtv" "/dev/fb1"  
        Option "VideoOverlay" "on"
        Option "XVideo" "1"
        BusID  "PCI:1:3:0"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "r128"
        Option      "UseFBDev" "true"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection

Section "Screen"
        Identifier "TV"
        Device "Hauppauge PVR 350 Framebuffer"
        Monitor "NTSC Monitor"
        DefaultDepth 24
        DefaultFbbpp 32
        Subsection "Display"
                Depth 24
                FbBpp 32
                Modes "720x480"
        EndSubsection
EndSection

Section "Monitor"
        Identifier "NTSC Monitor"
        HorizSync 30-68
        VertRefresh 50-120
        DisplaySize 183 122
        Mode "720x480"
                # D: 34.563 MHz, H: 37.244 kHz, V: 73.897 Hz
                DotClock 34.564
                HTimings 720 752 840 928
                VTimings 480 484 488 504
                Flags   "-HSync" "-VSync"
        EndMode
EndSection


I'm not sure what's going on, but I feel like I'm close!

Thanks,
Henry

On Fri, 2007-03-09 at 08:54 -0500, Henry Leinhos wrote:
> Well, It all seems to be working! (more or less)

> 
> After all that, I had to downgrade my ATrpms ivtv packages to 0.10.0
> (along with an older video4linux-kmdl package for the 2.6.19-1.2911
> kernel) since there seems to be some question as to the proper API now
> that V4L is taking over the kernel module part.
> 
> Now I get (mostly) everything working, except for the X has messed-up
> colors related to endian issues (what patches are out there for the
> latest ivtv_xdriver?).
> 
> My machine is only a 300MHz G3 (ppc750), but it can record a single
> channel without much cpu load.  I'm getting some pauses during playback,
> but those may be related to other system settings.
> 
> Cool!
> 
> Thanks to all,
> Henry



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

Reply via email to