[Intel-gfx] PAL output grey

ykzhao yakui.zhao at intel.com
Mon Sep 21 04:37:34 CEST 2009


On Mon, 2009-09-21 at 01:39 +0800, Wilfried Holzke wrote:
> Hi,
> 
> > Wilfried Holzke wrote on Friday, September 18, 2009 4:44 AM:
> >> Hi,
> >>
> >>> On Thu, Sep 17, 2009 at 22:29:47 +0200, Wilfried Holzke wrote:
> >>>
> >>>> If I run "xrandr --prop" I got a list of the available video modes,
> >>>> that is working. I connected the tv-out (svideo) to my terratec
> >>>> grabby and select "NTSC" (for input), there I got a colored video
> >>>> input. How can I change the intel card tv-out to "PAL"?
> >>>>
> >>> from my xrandr --prop output:
> >>>         mode:   NTSC-M
> >>>                 supported: NTSC-M       NTSC-443     NTSC-J      
> >>>                            PAL-M PAL-N        PAL         
> >>>                            480p at 59.94Hz 480p at 60Hz 576p        
> >>>                            720p at 60Hz    720p at 59.94Hz 720p at 50Hz
> >>> 1080i at 50Hz   1080i at 60Hz   1080i at 59.94H 
> >>>
> >>> So, if I wanted to change it to PAL, I'd use:
> >>> $ xrandr --output TV1 --set mode PAL
> >> Strange... I don't get such a list.
> >> Which version of kernel and xorg ... etc. do you use?
> > 
> > I guess you are hitting http://bugs.freedesktop.org/show_bug.cgi?id=22891. It's fixed in drm-intel-next. I'm not sure if it's in Linus's tree yet.
This is not related with the bug 22891.
On this box the integrated TV is used. But the issue in bug 22891 is
related with SDVO-TV.
> I patched my kernel (2.6.31) with "next-20090918". Now I get the mode
> output. But if I want to set "PAL" with "xrandr --output TV1 --set mode
> PAL" nothing happens. I could also execute something like "xrandr
> --output TV1 --set mode asdf". After running "xrandr --prop" I see
> "mode: asdf".  I'm a little bit confused. Any hints to get this working?
thanks for your test.
I also try the command of "xrandr --output TV1 --set mode asdf" on my
box and reproduce this issue.

How about changing the mode after you change the tv_format property?

This error is related with the our driver. After checking the source
code it seems that the property is firstly updated before check. 

I will try to fix this issue.
Thanks.
> 
> regards
> 
>   Wilfried
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx




More information about the Intel-gfx mailing list