From: Jani Nikula <jani.nikula@linux.intel.com>
To: vinoth eswaran <evinoth1206@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, "Syrjala,
Ville" <ville.syrjala@intel.com>
Subject: Re: i915 driver on Minnow board - 1920x1200 resolution not working
Date: Tue, 21 Jun 2016 17:50:20 +0300 [thread overview]
Message-ID: <87bn2ua95f.fsf@intel.com> (raw)
In-Reply-To: <CAJst-kFCmQp6Vwy5erKXMF--BTprw4BJph1rcxD8wjEDgO7xww@mail.gmail.com>
On Tue, 21 Jun 2016, vinoth eswaran <evinoth1206@gmail.com> wrote:
> On Tue, Jun 21, 2016 at 12:54 PM, Jani Nikula
> <jani.nikula@linux.intel.com> wrote:
>> On Tue, 21 Jun 2016, vinoth eswaran <evinoth1206@gmail.com> wrote:
>>> On Tue, Jun 21, 2016 at 11:35 AM, Jani Nikula
>>> <jani.nikula@linux.intel.com> wrote:
>>>> On Tue, 21 Jun 2016, vinoth eswaran <evinoth1206@gmail.com> wrote:
>>>>> On Tue, Jun 21, 2016 at 10:17 AM, Jani Nikula
>>>>> <jani.nikula@linux.intel.com> wrote:
>>>>>> On Tue, 21 Jun 2016, vinoth eswaran <evinoth1206@gmail.com> wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I am currently working on an embedded project using Minnowboard max. I
>>>>>>> have builded a customized Linux kernel-v4.4 and using u-boot (latest
>>>>>>> version) as Boot loader.
>>>>>>>
>>>>>>> The VESA driver in the u-boot takes more time to initialize,so I have
>>>>>>> disabled it. I am passing the kernel parameters "video=" to enable the
>>>>>>> HDMI port to which a monitor is connected.
>>>>>>
>>>>>> Is is a DVI display?
>>>>> Its an LED Monitor - LG 24EB23.
>>>>> The monitor supports the HD resolution.
>>>>
>>>> How do you connect the display? Is it HDMI directly or using the DVI
>>>> connector?
>>>>
>>> Sorry initially I got the question wrongly.
>>> Micro HDMI connector to the board and then HDMI-DVI cable to connect
>>> to the monitor.
>>
>> Single link DVI is limited to 165 Mhz. It *might* work with CVT and
>> reduced blanking. Please try video=HDMI-A-1:1920x1200@60RMD as the mode.
>>
>> I'm surprised the display doesn't report that via EDID to begin with;
>> what does it do without the video parameter on the command line?
>
> The display is not coming up now. Also without no video parameter,
> the display is not coming up.
> I checked the status of card-0* in /sys/class/drm all the three
> connectors are listed as disconnected.
>
> I have attached the drm driver logs for your reference.
Gets too noisy to debug here. Please file a bug at [1].
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-21 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 7:09 i915 driver on Minnow board - 1920x1200 resolution not working vinoth eswaran
2016-06-21 8:17 ` Jani Nikula
2016-06-21 8:51 ` vinoth eswaran
2016-06-21 9:35 ` Jani Nikula
2016-06-21 10:36 ` vinoth eswaran
2016-06-21 10:54 ` Jani Nikula
2016-06-21 11:07 ` vinoth eswaran
2016-06-21 14:50 ` Jani Nikula [this message]
2016-06-22 7:46 ` vinoth eswaran
2016-06-22 8:01 ` Jani Nikula
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=87bn2ua95f.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=evinoth1206@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@intel.com \
/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