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" <[email protected]
<mailto:[email protected]>> 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"
<[email protected] <mailto:[email protected]>
>> <mailto:[email protected]
<mailto:[email protected]>>> wrote:
>> >
>> > On 02/28/2013 08:34 AM, Andrei Gherzan wrote:> On Thu, Feb 28, 2013
>> at 5:30 PM, Eric Nelson
>> > > <[email protected]
<mailto:[email protected]>
>> <mailto:[email protected]
<mailto:[email protected]>>
>> >
>> > > <mailto:[email protected]
<mailto:[email protected]>
>>
>> <mailto:[email protected]
<mailto:[email protected]>>>> 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
>> > > <[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
>> <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>> 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
>> > [email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
>> > and not [email protected]
<mailto:[email protected]>
>> <mailto:[email protected]
<mailto:[email protected]>>.
>>
>> >
>>
>> 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
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale