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: Wed, 5 Apr 2017 15:05:47 +0200 [thread overview]
Message-ID: <20170405130547.GA19747@amethyst.visucore.com> (raw)
In-Reply-To: <CAOMZO5C9NwWnKLucDrprw067SwuXfiY16fPg1NABSyy_EGFYUQ@mail.gmail.com>
On Wed, Apr 05, 2017 at 09:50:23AM -0300, Fabio Estevam wrote:
> On Sat, Apr 1, 2017 at 6:40 PM, Fabio Estevam <festevam@gmail.com> 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.
> >
> > I will try to locate such monitor in the office next week and try it again.
>
> Finally had a chance to test it and I can see both U-Boot logo and
> kernel penguin correctly on my monitor.
Ok, thanks for testing.
To be clear: was this result with v3.x, or with mainline?
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-05 13:05 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
2017-04-05 12:50 ` Fabio Estevam
2017-04-05 13:05 ` Wladimir J. van der Laan [this message]
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=20170405130547.GA19747@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