From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Chris Healy <cphealy@gmail.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: DVI output on i.MX51 EVP board not working?
Date: Sun, 2 Apr 2017 16:03:56 +0200 [thread overview]
Message-ID: <20170402140356.GA10486@amethyst.visucore.com> (raw)
In-Reply-To: <CAOMZO5CMhF7Taaaex-k9a+L76YLtcwGAHLcEcMdk1kdkb3PQJA@mail.gmail.com>
On Sat, Apr 01, 2017 at 06:40:52PM -0300, Fabio Estevam wrote:
> Hi Wladimir,
>
> On Fri, Mar 31, 2017 at 2:36 AM, Wladimir J. van der Laan
> <laanwj@gmail.com> wrote:
>
> > - Went as far back as kernel v4.0, even to v3.12 or so (commit 493a863, "ARM:
> > dts: imx51-babbage: Make DVI and WVGA panel functional"). No difference. So nothing to
> > bisect, unfortunately.
>
> It was a long time I worked on this commit and it worked well for me
> on an old DVI monitor.
An extra data point: I tried with an older monitor (max 1280x1024) w/ DVI to
DVI cable, exactly the same behavior: u-boot shows output but "no signal" when
kernel boots. I was not able to go all the way back though, and only tested
this with mainline.
> I will try to locate such monitor in the office next week and try it again.
Thanks!
Regards,
Wladimir
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-02 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 5:36 DVI output on i.MX51 EVP board not working? Wladimir J. van der Laan
2017-03-31 10:02 ` Philipp Zabel
2017-03-31 15:58 ` Wladimir J. van der Laan
2017-04-01 21:40 ` Fabio Estevam
2017-04-02 14:03 ` Wladimir J. van der Laan [this message]
2017-04-05 12:50 ` Fabio Estevam
2017-04-05 13:05 ` Wladimir J. van der Laan
2017-04-05 13:11 ` Fabio Estevam
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=20170402140356.GA10486@amethyst.visucore.com \
--to=laanwj@gmail.com \
--cc=cphealy@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.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