Might that be a PAL vs. NTSC issue? Xvinfo shows the PAL-Resolution as max.
xv size while ivtv-fb et al are correct about their NTSC assumptions.

Just thinking.
Martin 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Andrew Kohlsmith
> Sent: Thursday, June 30, 2005 1:22 AM
> To: ivtv-devel@lists.sourceforge.net
> Subject: Re: [ivtv-devel] Re: Ioctl IVTV_IOC_PREP_FRAME_YUV 
> returned failed Error Invalid argument (was mplayer with -vo 
> xv: signal 6)
> 
> On Wednesday 29 June 2005 11:56, John Harvey wrote:
> > I'm busy tonight but i'll try to remember to look at this 
> and suggest 
> > something tomorrow.
> 
> Dmesg output from a fresh (hard) boot, modprobe ivtv (I have 
> nothing in my modules.conf nor modprobe.conf so no options 
> were passed):
> 
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.3.4 (p) loading
> ivtv: Linux version: 2.6.9 preempt K7 REGPARM gcc-3.3
> ivtv: In case of problems please include the debug info
> ivtv: between the START INIT IVTV and END INIT IVTV lines when
> ivtv: mailing the ivtv-devel mailinglist.
> ivtv: Autodetected WinTV PVR 350 card
> ivtv: Found an iTVC15 based chip
> ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 17
> ivtv: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv: XXX PCI device: 0x0651 vendor: 0x1039
> tveeprom: Hauppauge: model = 48132, rev = J323, serial# = 6813993
> tveeprom: tuner = Philips FM1236 (idx = 23, type = 2)
> tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> tveeprom: audio_processor = MSP3440 (type = 11)
> ivtv: i2c attach [client=tveeprom[50],ok]
> ivtv: Tuner Type 2, Tuner formats 0x00001000, Radio: yes, 
> Model 0x00a93493, Revision 0x00000001
> ivtv: NTSC tuner detected
> ivtv: Radio detected
> tuner: Ignoring new-style parameters in presence of obsolete ones
> tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> ivtv: i2c attach [client=(tuner unset),ok]
> saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
> saa7115: detecting saa7115 client on address 0x42
> saa7115: writing init values
> ivtv: i2c attach [client=saa7115[50],ok]
> saa7115: status: (1E) 0x48, (1F) 0xc0
> saa7127: Ignoring new-style parameters in presence of obsolete ones
> saa7127: video encoder driver version V 0.3 loaded
> saa7127: detecting saa7127 client on address 0x88
> saa7127: Selecting NTSC video Standard
> saa7127: Selecting S-Video+Composite
> saa7127: Turn WSS off
> saa7127: Widescreen Mode 4:3 Full Format
> saa7127: Selecting Normal Encoder Input
> saa7127: Enable Video Output
> ivtv: i2c attach [client=saa7127[50],ok]
> msp34xx: ivtv version
> msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple 
> (D) mode, simpler
> (G) no-thread mode
> msp34xx: $Id$ compiled on: May 23 2005 17:35:04
> ivtv: i2c attach [client=MSP3448W-A2,ok]
> ivtv: Encoder revision: 0x02040011
> ivtv: Decoder revision: 0x02020023
> ivtv: Configuring WinTV PVR 350 card with 10 streams
> ivtv: Registered v4l2 device, streamtype 0 minor 0
> ivtv: Create DMA stream 0 using 128 16384 byte buffers  0 kbytes total
> ivtv: Registered v4l2 device, streamtype 1 minor 32
> ivtv: Create DMA stream 1 using 20 103680 byte buffers  0 kbytes total
> ivtv: Registered v4l2 device, streamtype 2 minor 224
> ivtv: Create DMA stream 2 using 40 52224 byte buffers  0 kbytes total
> ivtv: Registered v4l2 device, streamtype 3 minor 24
> ivtv: Create DMA stream 3 using 455 4608 byte buffers  0 kbytes total
> ivtv: Registered v4l2 device, streamtype 4 minor 64
> ivtv: Create stream 4
> ivtv: Registered v4l2 device, streamtype 5 minor 16
> ivtv: Create DMA stream 5 using 16 65536 byte buffers  0 kbytes total
> ivtv: Registered v4l2 device, streamtype 6 minor 228
> ivtv: Create DMA stream 6 using 1024 2048 byte buffers  0 kbytes total
> ivtv: Registered v4l2 device, streamtype 7 minor 232
> ivtv: Create stream 7
> ivtv: Registered v4l2 device, streamtype 8 minor 48
> ivtv: Create DMA stream 8 using 20 103680 byte buffers  0 kbytes total
> ivtv: Create DMA stream 9 using 32 65536 byte buffers  0 kbytes total
> ivtv: Setting Tuner 2
> tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and 
> compatibles)) by ivtv i2c driver #0
> saa7115: decoder set input (4)
> saa7115: now setting Composite input
> ivtv: ivtv_enc_thread: pid = 2705, itv = 0xe0aa3060
> ivtv: ivtv_enc_vbi_thread: pid = 2706, itv = 0xe0aa3060
> ivtv: ivtv_dec_thread: pid = 2707, itv = 0xe0aa3060
> ivtv: ivtv_dec_vbi_thread: pid = 2708, itv = 0xe0aa3060
> ivtv: Setting audio matrix to input 3, output 1
> ivtv: Switching standard to NTSC.
> saa7115: decoder set norm NTSC
> saa7115: set audio: 0x01
> saa7127: Setting Encoder Video Standard
> saa7127: Set NTSC Video Mode
> saa7127: Selecting NTSC video Standard
> ivtv: Initialized WinTV PVR 350, card #0
> ivtv: ====================  END INIT IVTV  ====================
> 
> 
> And after modprobe'ing ivtv-fb:
> 
> ivtv-osd: Framebuffer module loaded (attached to ivtv card id 0)
> ivtv-osd: Framebuffer is at decoder-relative address 
> 0x00510000 and has 1704960 bytes.
> ivtv-osd: screen coords: [0 0] -> [720 480]
> ivtv-osd: original global alpha = 208
> ivtv-osd: current OSD state = 39
> ivtv-osd: new global alpha = 208 (1 255 0)
> ivtv-osd: framebuffer at 0xdd510000, mapped to 0xe1990000, size 1350k
> ivtv-osd: mode is 720x480x32, linelength=2880
> Console: switching to colour frame buffer device 90x30
> ivtv-osd: fb0: iTVC15 TV out frame buffer device
> ivtv: Allocate DMA stream 9 using 32 65536 byte buffers  
> 2097152 kbytes total
> 
> After dd'ing as you instructed:
> 
> ivtv: Allocate DMA stream 0 using 128 16384 byte buffers  
> 2097152 kbytes total
> saa7115: decoder disable output
> saa7115: decoder enable output
> ivtv: Allocate DMA stream 5 using 16 65536 byte buffers  
> 1048576 kbytes total
> ivtv: Allocate DMA stream 6 using 1024 2048 byte buffers  
> 1048576 kbytes total
> 
> No futher changes in dmesg after loading X or running 
> mplayer, but mplayer's output is a little (but not 
> significantly) different:
> 
> X11 error: BadImplementation (server does not implement operation)
> 
> 
> MPlayer interrupted by signal 6 in module: vo_check_events
> - MPlayer crashed. This shouldn't happen.
>   It can be a bug in the MPlayer code _or_ in your drivers 
> _or_ in your
>   gcc version. If you think it's MPlayer's fault, please read
>   DOCS/HTML/en/bugreports.html and follow the instructions 
> there. We can't and
>   won't help unless you provide this information when 
> reporting a possible bug.
> X11 error: BadImplementation (server does not implement operation)
> 
> 
> MPlayer interrupted by signal 6 in module: uninit_vo
> alsa-uninit: pcm closed
> X Error of failed request:  BadImplementation (server does 
> not implement 
> operation)
>   Major opcode of failed request:  139 (XVideo)
>   Minor opcode of failed request:  19 ()
>   Serial number of failed request:  83
>   Current serial number in output stream:  91
> X Error of failed request:  BadImplementation (server does 
> not implement 
> operation)
>   Major opcode of failed request:  139 (XVideo)
>   Minor opcode of failed request:  19 ()
>   Serial number of failed request:  84
>   Current serial number in output stream:  91
> X Error of failed request:  BadImplementation (server does 
> not implement 
> operation)
>   Major opcode of failed request:  139 (XVideo)
>   Minor opcode of failed request:  19 ()
>   Serial number of failed request:  85
>   Current serial number in output stream:  91
> X Error of failed request:  BadImplementation (server does 
> not implement 
> operation)
>   Major opcode of failed request:  139 (XVideo)
>   Minor opcode of failed request:  19 ()       
>                                   Serial number of failed request:  86
>   Current serial number in output stream:  91
> X Error of failed request:  BadImplementation (server does 
> not implement 
> operation)
>   Major opcode of failed request:  139 (XVideo)
>   Minor opcode of failed request:  19 ()
>   Serial number of failed request:  87
>   Current serial number in output stream:  91
> 
> And x.org's output from that:
> GetModeLine - scrn: 0 clock: 34564
> GetModeLine - hdsp: 720 hbeg: 752 hend: 840 httl: 928
>               vdsp: 480 vbeg: 484 vend: 488 vttl: 504 flags: 10
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
> Ioctl IVTV_IOC_PREP_FRAME_YUV returned failed Error Invalid argument
>         bitsPerPixel=32, depth=24, defaultVisual=TrueColor
>         mask: ff0000,ff00,ff, offset: 16,8,0
> 
> 
> Oh and xvinfo's output if that helps:
> 
> X-Video Extension version 2.2
> screen #0
>   Adaptor #0: "PVR350"
>     number of ports: 1
>     port base: 56
>     operations supported: PutImage
>     supported visuals:
>       depth 24, visualID 0x22
>       depth 24, visualID 0x23
>       depth 24, visualID 0x24
>       depth 24, visualID 0x25
>     no port attributes defined
>     maximum XvImage size: 768 x 576
>     Number of image formats: 1
>       id: 0x32315659 (YV12)
>         guid: 59563132-0000-0010-8000-00aa00389b71
>         bits per pixel: 12
>         number of planes: 3
>         type: YUV (planar)
> 
> Hope this is useful.  :-)
> 
> -A.
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> 
> 



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to