On Tue, 2007-05-29 at 10:33 +0200, Hans Verkuil wrote:
> > On May 22, 2007, at 12:04 PM, Hans Verkuil wrote:
> >
> >>> On May 22, 2007, at 3:26 AM, Hans Verkuil wrote:
> >>>
> >>>>> On May 19, 2007, at 2:14 PM, Hans Verkuil wrote:
> >>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> I would appreciate it if people could start testing the latest
> >>>>>> ivtv on
> >>>>>> the 0.10 branch, available here:
> >>>>>
> >>>>> Excellent! Always looking forward to some new & improved code.
> >>>>>
> >>>>>> The current driver has a problem with copying data from the MPEG
> >>>>>> card to
> >>>>>> memory that are done using PIO instead of DMA (for good reasons).
> >>>>>> Unfortunately PIO accesses are slow, so too much time is spent
> >>>>>> inside
> >>>>>> the interrupt handler. This can lead to missing clock ticks and
> >>>>>> problems with remotes (key hits that are missed).
> >>>>>
> >>>>> The missing ticks have certainly gone away. My clock keeps up just
> >>>>> fine while making recordings now.
> >>>>>
> >>>>>> However, I did not have much time to test it thoroughly, so I'd
> >>>>>> very
> >>>>>> much appreciate it if people could start testing this and report
> >>>>>> whether or not any new problems were introduced.
> >>>>>
> >>>>> Well, as it seems, I am still having the same problems (on PPC)
> >>>>> with
> >>>>> the radio patch that was posted a while back. Regressing that patch
> >>>>> from the 0.10 branch yields a perfectly stable and usable ivtv
> >>>>> subsystem and machine.
> >>>>>
> >>>>> To recap on what happened post-radio patch, if I'm recording
> >>>>> with the
> >>>>> PVR-350 and try to use the xdriver (on the 350's TV-out) for some
> >>>>> mplayer -xv playback, the screen will go black and there will be
> >>>>> audio for a second, then mplayer crashes. Here's some more info on
> >>>>> what mplayer (and X) complain about:
> >>>>
> >>>> Are you recording the radio or TV? If recording from TV, did you
> >>>> do a
> >>>> radio capture earlier or was radio not used at all?
> >>>
> >>> Radio was not used at all; I've never configured a program to use it.
> >>
> >> Weird. Please test the following: load the driver (so that you are
> >> certain
> >> it is cleanly started and not used by any program), then tune to a
> >> frequency using ivtv-tune or v4l2-ctl and capture something using 'cat
> >> /dev/video0 >x.mpg'. Is this capture correct or also corrupt?
> >
> > This produces a correct MPEG2 capture.
> >
> >> If the mpeg is correct, then please use ivtv-radio to access the
> >> radio (it
> >> probably is even enough to just do 'cat /dev/radio' and break it off).
> >> Once done using the radio, try to capture video again. If it is now
> >> wrong,
> >> then it is likely to be caused by the radio patch.
> >
> > I then used `ivtv-radio -s` to get a list of all the available
> > channels, and the entire system hung. Curiously, if I reload the
> > driver then run `ivtv-radio -s` before anything else, it doesn't hang.
> >
> > Let me know if there's anything else I can do,
>
> Can you test whether just changing the audio sampling frequency using
> 'v4l2-ctl -c audio_sampling_frequency=0' will also cause problems? So just
> run this and check if capturing from the TV (no radio involved in this
> test) will work or not. I'm wondering if there is an endian problem when
> the sampling freq. is changed. This code is now called for radio as well,
> so any endian problem is now triggered when using the radio.
>
> Explicitly changing the sampling freq. should trigger such a bug for any
> ivtv version (with or without the radio patch).
>
> I looked through the code and didn't see any obvious endianness problem,
> but this test should reveal whether there are any or not.
>
> Regards,
>
> Hans
>
Testing the latest 0.10 branch everything works OK
also changing audio sampling frequency tests OK
Looking forward for the 2.6.22 release. Using 2.6.21 actually. Any idea
when it will be release?
Regards
Roger
below dmesg result
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.10.3 (development snapshot compiled on Wed 30 May 2007
11:52:32 AM CEST) loading
ivtv: Linux version: 2.6.21rt3 SMP preempt mod_unload K7 REGPARM
4KSTACKS
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)
ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 17 (level, low) -> IRQ 18
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0030bd051800125a]
ivtv0: Encoder revision: 0x02060039
ivtv0: Decoder revision: 0x02020023
tveeprom 1-0050: Hauppauge model 48139, rev K2B7, serial# 9867696
tveeprom 1-0050: tuner model is Philips FM1216ME MK5 (idx 117, type 38)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 1-0050: audio processor is MSP4418 (idx 25)
tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
tveeprom 1-0050: has radio, has IR receiver, has no IR transmitter
ivtv0: Autodetected Hauppauge WinTV PVR-350
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
scsi 1:0:0:0: Direct-Access ST332082 0A 0000 PQ: 0
ANSI: 0
usb-storage: device scan complete
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
scsi 0:0:0:0: Direct-Access WDC WD25 00JB-00GVC0 08.0 PQ: 0
ANSI: 0
usb-storage: device scan complete
scsi 1:0:0:0: Attached scsi generic sg0 type 0
scsi 0:0:0:0: Attached scsi generic sg1 type 0
saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver
#0)
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
sda: Mode Sense: 27 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
sda: Mode Sense: 27 00 00 00
sda: assuming drive cache: write through
sda: sda1
sd 1:0:0:0: Attached scsi disk sda
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sd 0:0:0:0: Attached scsi disk sdb
saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
msp3400 1-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0)
msp3400 1-0040: MSP4418G-B3 supports nicam and radio, mode is autodetect
and autoselect
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 1-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 18 (level, low) -> IRQ 19
Consumer PCM code does not work well at the moment --jk
ivtv: ==================== END INIT IVTV ====================
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
