From: Gabriel C <nix.or.die@googlemail.com>
To: "Ma, Ling" <ling.ma@intel.com>
Cc: Dave Airlie <airlied@gmail.com>, Dave Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
Keith Packard <keithp@keithp.com>, Eric Anholt <eric@anholt.net>
Subject: Re: [git pull] drm fixes + intel display port
Date: Sat, 27 Jun 2009 15:39:08 +0200 [thread overview]
Message-ID: <4A4620FC.5030708@googlemail.com> (raw)
In-Reply-To: <8FED46E8A9CA574792FC7AACAC38FE7701E6AAB162@PDSMSX501.ccr.corp.intel.com>
Ma, Ling wrote:
>> -----Original Message-----
>> From: Dave Airlie [mailto:airlied@gmail.com]
>> Sent: 2009年6月26日 7:32
>> To: Gabriel C
>> Cc: Dave Airlie; Ma, Ling; LKML; Keith Packard; Eric Anholt
>> Subject: Re: [git pull] drm fixes + intel display port
>>
>> On Thu, Jun 25, 2009 at 12:31 AM, Gabriel C<nix.or.die@googlemail.com> wrote:
>>> [ forgot to CC LKML , sorry ]
>>>
>>> Gabriel C wrote:
>>>
>>>> 2009/6/24 Dave Airlie <airlied@linux.ie>:
>>>>> Hi Linus,
>>>>>
>>>>> Please pull the 'drm-fixes' branch from
>>>>> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
>> drm-fixes
>>>> Hi Dave ,
>>>>
>>>> I own an DQ45CB Intel motherboard. When enabling KMS with kernels from
>>>> 2.6.29* to current git / linux-next on that board
>>>> I don't get any console. My Monitor is saying 'No signal' , however
>>>> once X starts up I can login in KDE/gnome etc.
>>>>
>>>> The monitor is connected with an DVI-I -> VGA connector.
>>>>
>>>> I found on the gfx mailing list the following patch from Ma Ling :
>>>>
>>>> http://lists.freedesktop.org/archives/intel-gfx/2009-May/002504.html
>>>>
>>>> which seems to fix my problem. With that patch applied I get a console
>>>> and everything works fine.
>>>>
>>>> However I still have such :
>>>>
>>>> [ 21.205449] i2c-adapter i2c-1: unable to read EDID block.
>>>> [ 21.205452] i915 0000:00:02.0: VGA-1: no EDID data
>>>>
>>>>
>>>> messages in my dmesg but it works.
>>>>
>>>>
>>>> Is there any reason why this patch never got merged ?
>> I don't think that patch is totally correct, it looks more like a lets
>> try everything approach, I'll cc more Intel folks and see what they can do.
>>
>> Dave.
>>
> Yes, I have refined the patch [Resend][PATCH 1/4] drm/i915: crt fetch EDID by DVI-I converter on G4x platform, and re-sent to mailing list. In that version we specified G4x platform which used GPIOD as port, which is wired to I2C bus of VGA or HDMI. Any comments from Eric?
You mean http://lists.freedesktop.org/archives/intel-gfx/2009-June/002955.html ? If is so I can confirm this patch is working on my
motherboard too.
However on current git ( 2.6.31-rc1-00114-g4075ea8-dirty ) Have some new drm errors/warnings I never got before:
...
[ 6.215535] [drm] Initialized drm 1.1.0 20060810
[ 6.354943] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6.354946] i915 0000:00:02.0: setting latency timer to 64
[ 6.367517] alloc irq_desc for 34 on node -1
[ 6.367520] alloc kstat_irqs on node -1
[ 6.367530] i915 0000:00:02.0: irq 34 for MSI/MSI-X
[ 6.372899] [drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-B
[ 6.375957] dp_aux_ch timeout status 0x514500c8
[ 6.375997] aux_ch failed -110
[ 6.378944] dp_aux_ch timeout status 0x514500c8
[ 6.378984] aux_ch failed -110
[ 6.384150] [drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-C
[ 6.387204] dp_aux_ch timeout status 0x514500c8
[ 6.387244] aux_ch failed -110
[ 6.390189] dp_aux_ch timeout status 0x514500c8
[ 6.390229] aux_ch failed -110
[ 6.417734] i2c-adapter i2c-1: unable to read EDID block.
[ 6.417736] i915 0000:00:02.0: VGA-1: no EDID data
[ 6.624401] dp_aux_ch timeout status 0x514500c8
[ 6.628947] allocated 1280x1024 fb: 0x02020000, bo ffff88007a136480
[ 6.630266] Console: switching to colour frame buffer device 160x64
[ 6.690944] [drm] DAC-6: set mode 1280x1024 20
[ 6.714585] fb0: inteldrmfb frame buffer device
[ 6.714587] registered panic notifier
....
[ 329.114444] i2c-adapter i2c-1: unable to read EDID block.
[ 329.114448] i915 0000:00:02.0: VGA-1: no EDID data
[ 329.421751] dp_aux_ch timeout status 0x514500c8
[ 329.424764] dp_aux_ch timeout status 0x514500c8
[ 329.462443] i2c-adapter i2c-1: unable to read EDID block.
[ 329.462446] i915 0000:00:02.0: VGA-1: no EDID data
[ 329.800624] dp_aux_ch timeout status 0x514500c8
[ 329.803636] dp_aux_ch timeout status 0x514500c8
[ 352.215440] i2c-adapter i2c-1: unable to read EDID block.
[ 352.215444] i915 0000:00:02.0: VGA-1: no EDID data
[ 352.523889] dp_aux_ch timeout status 0x514500c8
[ 352.526902] dp_aux_ch timeout status 0x514500c8
[ 358.049548] i2c-adapter i2c-1: unable to read EDID block.
[ 358.049552] i915 0000:00:02.0: VGA-1: no EDID data
[ 358.358469] dp_aux_ch timeout status 0x514500c8
[ 358.361488] dp_aux_ch timeout status 0x514500c8
[ 358.412680] i2c-adapter i2c-1: unable to read EDID block.
[ 358.412684] i915 0000:00:02.0: VGA-1: no EDID data
[ 358.721347] dp_aux_ch timeout status 0x514500c8
[ 358.724361] dp_aux_ch timeout status 0x514500c8
....
Gabriel
prev parent reply other threads:[~2009-06-27 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 6:42 [git pull] drm fixes + intel display port Dave Airlie
[not found] ` <1820d69d0906240715v6c3591c4x30ee87e9ec8774f7@mail.gmail.com>
2009-06-24 14:31 ` Gabriel C
2009-06-25 23:31 ` Dave Airlie
2009-06-26 13:25 ` Ma, Ling
2009-06-27 13:39 ` Gabriel C [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4620FC.5030708@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=eric@anholt.net \
--cc=keithp@keithp.com \
--cc=ling.ma@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox