From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: meta-freescale@yoctoproject.org,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Issues with sync-boundary-changes.patch on imx6qsabrelite
Date: Thu, 28 Feb 2013 12:39:39 -0700 [thread overview]
Message-ID: <512FB27B.2030305@boundarydevices.com> (raw)
In-Reply-To: <CAK18fxFLEOqizOmAM0vzzC4rPByCcTsWmeNSj5bW-fM=hgRPNg@mail.gmail.com>
Hi Andre,
On 02/28/2013 11:03 AM, Andrei Gherzan wrote:
> --
> Andrei Gherzan
> m: +40.744.478.414 | f: +40.31.816.28.12
> On Feb 28, 2013 7:58 PM, "Eric Nelson" <eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>> wrote:
> >
> > On 02/28/2013 10:47 AM, Andrei Gherzan wrote:
> >>
> >> --
> >> Andrei Gherzan
> >> m: +40.744.478.414 | f: +40.31.816.28.12
> >> On Feb 28, 2013 7:33 PM, "Eric Nelson"
> <eric.nelson@boundarydevices.com <mailto:eric.nelson@boundarydevices.com>
> >> <mailto:eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>>> wrote:
> >> >
> >> > On 02/28/2013 08:34 AM, Andrei Gherzan wrote:> On Thu, Feb 28, 2013
> >> at 5:30 PM, Eric Nelson
> >> > > <eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>
> >> <mailto:eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>>
> >> >
> >> > > <mailto:eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>
> >>
> >> <mailto:eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>>>> wrote:
> >> > >
> >> > > Hi Otavio and Andrei,
> >> > > On 02/28/2013 08:01 AM, Otavio Salvador wrote:
> >> > > On Thu, Feb 28, 2013 at 11:42 AM, Andrei Gherzan
> >> > > <andrei@gherzan.ro <mailto:andrei@gherzan.ro>
> <mailto:andrei@gherzan.ro <mailto:andrei@gherzan.ro>>
> >> <mailto:andrei@gherzan.ro <mailto:andrei@gherzan.ro>
> <mailto:andrei@gherzan.ro <mailto:andrei@gherzan.ro>>>> wrote:
> >> > >
> >> > > While using imx6, I faced 2 issues after updating the
> >> > > kernel to ver. / rel.
> >> > > 1.1.0:
> >> > >
> >> >
> >> > Hi Andrei,
> >> >
> >> > I think you wanted to send this to
> >> > meta-freescale@yoctoproject.org
> <mailto:meta-freescale@yoctoproject.org>
> <mailto:meta-freescale@yoctoproject.org
> <mailto:meta-freescale@yoctoproject.org>>
> >> > and not meta-fsl-arm@googlegroups.com
> <mailto:meta-fsl-arm@googlegroups.com>
> >> <mailto:meta-fsl-arm@googlegroups.com
> <mailto:meta-fsl-arm@googlegroups.com>>.
> >>
> >> >
> >>
> >> Ok. I'm confused now.
> >>
> > Hi Andrei,
> >
> > There was apparently a Google group before the ML at Yocto Project was
> > created.
> >
> > I'm testing now and seeing some weirdness related to 1080P beyond the
> > vmalloc and fbmem thing.
> >
> > 720P seems to work fine.
> >
>
> Aaa. Forgot to mention this. I can confirm it.
>
I've finally been able to reproduce the issue you reported (lockup
during boot), and it's really odd. It appears to only occur if I
leave off a couple of clauses from the kernel command-line:
video=mxcfb1:off video=mxcfb2:off
Without that, something in the kernel startup seems to create
another frame-buffer on /dev/fb2:
--------/sys/class/graphics/fb0
DISP3 BG - DI1
U:1280x720p-60
--------/sys/class/graphics/fb1
DISP3 FG
--------/sys/class/graphics/fb2
name: DISP4 BG
mode: D:1280x800p-60
FWIW, my other display problem stemmed from me running
a kernel that had the Vivante driver built as a module
instead of statically into the kernel.
Regards,
Eric
next prev parent reply other threads:[~2013-02-28 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK18fxF8UjHgX=fu9ZO8c_uLsnkOekxNCtgAgJMpLmqCKdUHSg@mail.gmail.com>
[not found] ` <CAP9ODKrpBg13Vs8o65NYhkHWKzQq7ju80-+Ewc8qHwuqBsTAoA@mail.gmail.com>
[not found] ` <512F7827.5040901@boundarydevices.com>
[not found] ` <CAK18fxFSsmHbwje=obkZgFO+rpCGamC337JT20khQ8CSBDdiNA@mail.gmail.com>
2013-02-28 17:33 ` Issues with sync-boundary-changes.patch on imx6qsabrelite Eric Nelson
2013-02-28 17:47 ` Andrei Gherzan
2013-02-28 17:58 ` Eric Nelson
2013-02-28 18:03 ` Andrei Gherzan
2013-02-28 19:39 ` Eric Nelson [this message]
2013-02-28 17:51 ` Otavio Salvador
2013-02-28 18:16 ` Eric Nelson
2013-02-28 18:27 ` Andrei Gherzan
2013-02-28 18:37 ` Eric Nelson
[not found] ` <CAK18fxHH01WMaD8ZitqYV3z1GikGsz4JEdht4v0p9S8u0EGWcQ@mail.gmail.com>
2013-03-01 14:13 ` Eric Nelson
[not found] ` <CAK18fxHLoPofOew2TcKXMj3tzHgVzu=aOU4D56rDnQLhcrJ_vw@mail.gmail.com>
2013-03-01 14:15 ` Eric Nelson
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=512FB27B.2030305@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=andrei@gherzan.ro \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.