[mythtv-users] PVR350 video out very slow (Nvidia way better)
Emmanuel Hislen
hislen at mindspring.com
Sat Feb 7 02:10:15 EST 2004
Oops, just found out that /dev/video16 was a plain file. I did:
# rm -f /dev/video16
# mknod -m 660 /dev/video16 c 81 16
# ls -l /dev |grep video
drwxr-xr-x 2 manu manu 4096 Jan 23 01:28 video
crw------- 1 manu root 81, 0 Sep 15 06:40 video0
crw------- 1 manu root 81, 1 Sep 15 06:40 video1
drwxr-xr-x 2 root root 4096 Jan 23 01:28 video1394
crw------- 1 manu root 81, 16 Feb 6 22:25 video16
crw------- 1 manu root 81, 2 Sep 15 06:40 video2
crw------- 1 manu root 81, 3 Sep 15 06:40 video3
I rebooted a couple of times.
Still doesn't work...
I also found out that once in a while when I reboot, ivtv cannot even
get the firmware (timeout), and then even the capture doesn't work. But
that's another story :-), and a reboot fixes it so that's good enough
for me.
Emmanuel Hislen wrote:
> Hi Torsten,
>
> I think you're right. Like I said I never ran the "dd" test before
> because I did not have the ivtvfbctl tool and I thought this could not
> work without it. Then I jumped to the real mythTV test, and seeing an
> image on TV proved me that it worked. But that's where I was mistaken
> I believe: it now seems that getting an image does not mean I am using
> the 350 decoder.
>
> I tried the dd test now and nothing happens :-(
> Now I feel like an idiot...
>
> I passed the test image test in the howto though:
>
> insmod saa7127 enable_output=1 output_select=0 test_image=1
>
> I got the color pattern on the TV screen.
>
> I also passed the "cat /dev/video0 > /tmp/test_capture.mpg" test with
> mplayer. But that'sthe input side.
>
> Now when I do:
>
> dd if=/dev/video0 of=/dev/video16 bs=65536
>
> Nothing...
>
> How do I know if /dev/video16 is the right one?
>
> Here's what I have:
>
> [root at fantasio dev]# ls -l /dev |grep video
> drwxr-xr-x 2 manu manu 4096 Jan 23 01:28 video
> crw------- 1 manu root 81, 0 Sep 15 06:40 video0
> crw------- 1 manu root 81, 1 Sep 15 06:40 video1
> drwxr-xr-x 2 root root 4096 Jan 23 01:28 video1394
> -rw-rw---- 1 manu root 4444096 Feb 6 21:14 video16
> crw------- 1 manu root 81, 2 Sep 15 06:40 video2
> crw------- 1 manu root 81, 3 Sep 15 06:40 vide
>
> Note every time I do the dd test video16 gets bigger. Looks like
> nobody is reading/removing content from it.
>
> Here's what I have from dmesg
>
> <<<<<<<<<<
> ...
> [saa7127.c: INFO]: SAA7127 video encoder driver loaded
> ivtv: version 0.1.9 (release) loading
> ivtv: SGarray_size = 340, DSGarray_size = 56
> ivtv: Found an iTVC15 based chip
> tuner: chip found @ 0xc2
> tuner(bttv): type forced to 2 (Philips NTSC (FI1236,FM1236 and
> compatibles)) [insmod]
> saa7127: Configuring encoder...<6>saa7114.c: starting probe for
> adapter ivtv i2c driver #0 (0x10005)
> saa7114.c: detecting saa7114 client on address 0x42
> saa7115.c: writing init values
> status: (1E) 0x50, (1F) 0xc0
> msp34xx: init: chip=MSP3448W-A2, has NICAM support
> msp3410: daemon started
> ivtv: Encoder revision: 0x02040011
> ivtv: Decoder revision: 0x02020023
> ivtv: Registered v4l2 device, minor 0
> ivtv: Registered v4l2 device, minor 32
> ivtv: Registered v4l2 device, minor 224
> ivtv: Registered v4l2 device, minor 16
> ivtv: Registered v4l2 device, minor 48
> ivtv: loaded
> ivtv-fb: Framebuffer module loaded (attached to ivtv card id 0)
> ivtv-fb: screen coords: [0 0] -> [720 480]
> ivtv-fb: original global alpha = 208
> ivtv-fb: new global alpha = 208
> ivtv-fb: current OSD state = 35
> ivtv-fb: warning: cannot reserve video memory at 0xd9510000
> ivtv-fb: framebuffer at 0xd9510000, mapped to 0xe3e73000, size 2818k
> ivtv-fb: mode is 720x480x32, linelength=2880
> Console: switching to colour frame buffer device 90x30
> fb0: iTVC15 TV out frame buffer device
> lirc_dev: IR Remote Control driver registered, at major 61
> bttv: driver version 0.7.107 loaded
> bttv: using 4 buffers with 2080k (8320k total) for capture
> bttv: Host bridge is PCI device 10de:01e0 (nVidia Corporation
> ...
>
>> >>>>>>>>>
>
>
> The part about "cannot reserve video memory" looks scary to me but
> I've seen it on some other peole's dmesg in the archives.
>
> Where can I find the video node used by the 350 tv out?
>
>
> Thanks a lot,
>
> Emmanuel.
>
>
> Torsten Schenkel wrote:
>
>>> I believe I did check this box. Hard to say it is outside the screen
>>> when
>>> using the tv-out of the 350 :-(
>>>
>>> But when I clicked it another menu appeared about /dev/video16, si I
>>> believe
>>> I did click it.
>>>
>>> I'll double check again :-)
>>
>>
>>
>> OK, I'll summarize:
>>
>> - You have X up and running on the pvr's tv-out
>>
>> So your fbx and pci settings are correct, otherwise your X would bail
>> out
>>
>> - You have the checkbox set to use the pvr's tv-out, otherwise you
>> wouldn't see the /dev/video16 field, as you stated you do.
>>
>> - Still Myth doesn't use the pvr's decoder, but tries to display the
>> video on the framebuffer
>>
>>
>> Did you test the pvr with the dd test? Does /dev/video16 exist. Does the
>> ivtv bind to some other device? It's always /dev/video[X] for input and
>> /dev/video[X+16] for output. So maybe you got the wrong device?
>>
>> Torsten
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
More information about the mythtv-users
mailing list