From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Shifted framebuffer after X11 starts on mx28
Date: Sat, 16 Mar 2013 21:00:38 +0000 [thread overview]
Message-ID: <201303162200.38990.marex@denx.de> (raw)
In-Reply-To: <201303162155.28230.marex@denx.de>
Dear Marek Vasut,
> Dear Fabio Estevam,
>
> > Hi,
> >
> > I am running 3.8.2 kernel on a mx28evk and when I start X11 I get a
> > "shifted" framebuffer.
> >
> > The framebuffer works well if X11 is not called.
> >
> > There is no issue with X11 when running with Freescale 2.6.35 kernel.
> >
> > Looking at drivers/video/mxsfb.c there is the following comment:
> > /*
> >
> > * It seems, you can't re-program the controller if it is still running.
> > * This may lead into shifted pictures (FIFO issue?).
> > * So, first stop the controller and drain its FIFOs
> > */
> >
> > So, it looks like that I am still facing this issue when X11 starts.
> >
> > If anyone has any suggestions, please let me know.
>
> This is not it, I almost hunted the bug down. Hang on.
>
> Basically check mxsfb_set_par() and observe fb_info->var.sync . It's set to
> "something" during regular framebuffer operation and it's set to "something
> else" during Xorg operation. And that's what causes it to get broken. I
> forced fb_info->var.sync to the "something" value by hardcoding it in
> kernel just now for a quick test and X works for me.
Uh, being in hacking-mode and replying to email doesn't work well together :-)
In my case, fb_info->var.sync is set to FB_SYNC_DATA_ENABLE_HIGH_ACT during
regular operation (framebuffer console), but if X11 starts, this fb_info-
>var.sync is forced to value 0 which causes the malfunction. Now back into
hacking-mode ;-)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-03-16 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 20:09 Shifted framebuffer after X11 starts on mx28 Fabio Estevam
2013-03-16 20:55 ` Marek Vasut
2013-03-16 21:00 ` Marek Vasut [this message]
2013-03-16 22:06 ` [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0 Marek Vasut
2013-03-16 22:38 ` Fabio Estevam
2013-03-18 18:23 ` Marek Vasut
2013-03-18 18:58 ` Greg KH
2013-03-18 21:31 ` Marek Vasut
2013-03-18 22:01 ` Jonathan Nieder
2013-03-18 22:17 ` Marek Vasut
2013-03-18 18:24 ` Marek Vasut
2013-03-19 5:51 ` Shawn Guo
2013-03-18 12:44 ` Shawn Guo
2013-03-18 12:52 ` Fabio Estevam
2013-03-18 13:01 ` Shawn Guo
2013-03-18 13:58 ` Marek Vasut
2013-03-18 14:06 ` Shawn Guo
2013-03-18 14:18 ` Marek Vasut
2013-03-18 14:31 ` Shawn Guo
2013-03-18 15:19 ` Marek Vasut
2013-03-19 5:48 ` Shawn Guo
2013-03-19 10:33 ` Marek Vasut
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=201303162200.38990.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).