Call for community testers for intel driver

[Jin, Gordon]

William Grzybowski wrote on Thursday, January 24, 2008 2:54 AM:
> On Jan 23, 2008 6:25 AM, Jin, Gordon <gordon.jin at intel.com> wrote:
>> William Grzybowski wrote on Tuesday, January 22, 2008 9:18 PM:
>> 
>>> Hi,
>>> 
>>> Jin, Gordon wrote:
>>>> Hi all,
>>>> 
>>>> We Intel Graphics driver team would like to make closer
>>>> relationship with community users and calling for interested users
>>>> (including OSV engineers) to join a new community testing program.
>>>> 
>>>> Background:
>>>> The main reason is that Intel team is not able to cover all
>>>> hardware configurations hence not able to reproduce or verify some
>>>> bugs as: 
>>>> -- some platforms are not covered by Intel validation team, mostly
>>>> i8xx. 
>>>> -- some bugs only appear on some specific models (e.g. bug#11103).
>>>> -- some bugs only appear on some specific monitors.
>>>> -- some hardware configurations (like TV-out) are not fully covered
>>>> by our limited hardware for testing.
>>> 
>>> Machine: Acer 5570Z
>>> 
>>> Chipset: 00:02.0 VGA compatible controller: Intel Corporation Mobile
>>> 945GM/GMS, 943/940GML Express   Integrated Graphics Controller (rev
>>> 03) 00:02.1 Display controller: Intel Corporation Mobile
>>> 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
>>> (rev 03) 
>>> Driver: From git repository (actually 2.2.0)
>>> Monitor VGA Output: I can test it with an LCD LG 720s
>>> S-video output with an PAL TV Sony triniton (actually outputing in
>>> gray scale) OS: Debian Unstable ( SID )
>> 
>> Thanks for your response. I've added your info into
>> http://intellinuxgraphics.org/community_members.html.
>> 
>> For the TV gray issue, does it work by the solution in
>> https://bugs.freedesktop.org/show_bug.cgi?id=12748 ?
> 
> Unfortunately it doesn't work.
> I already tried to set all the others formats without success, stays
> in gray scale.
> I tried to change the format on my TV (NTSC, PAL-N, PAL-M, auto) but
> it makes no difference.
> My S-video output works fine on Windows, so I guess it has to be a
> driver issue. I'm able to do whatever you want me to do :)

I haven't seen such a bug report. Could you file a one?

Thanks
Gordon