All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yannick Calmettes <yannick.calmettes@analogway.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: QT 5.2.1 and eglfs 0x3003 error
Date: Mon, 13 Oct 2014 09:20:27 +0200	[thread overview]
Message-ID: <543B7D3B.6030108@analogway.com> (raw)
In-Reply-To: <20141010171609.0334f2e6@e6520eb.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

Hi Eric,

This patch is already include in the Yocto release I use. So this is not 
the same problem. Maybe eglfs cannot use 24 bits framebuffer ?

I forgot to say that I use framebuffer configuration (no X11 or Wayland).

Yannick
**
Le 10/10/2014 17:16, Eric Bénard a écrit :
> Hi Yannick,
>
> Le Fri, 10 Oct 2014 17:06:24 +0200,
> Yannick Calmettes <yannick.calmettes@analogway.com> a écrit :
>> I've encountered a strange error with QT 5.2.1 and eglfs platform. When
>> I launch a Qt5_CinematicExperience demo (and any other Qt apps) I have
>> an error "EGL Error : Could not create the egl surface: error = 0x3003".
>> In fact this error occurred only when the framebuffer is configured in
>> 24bpp. In 32bpp or 16bpp the demo works correctly. The problem is that
>> in my real product we use a 24bpp LCD screen.
>>
>> Is someone already encountered this problem ?
>>
>> Yannick
>>
>> I use "imx-3.10.31-1.1.0_beta" branch with a MCIMX6Q-SDB board
>> (MACHINE=imx6qsabresd). I run the fsl-image-qt5 image and start the demo
>> with "Qt5_CinematicExperience -platform eglfs".
>>   
> maybe you can try this patch :
> http://patchwork.openembedded.org/patch/66349/
>
> Eric
>   


 

[-- Attachment #2: Type: text/html, Size: 2701 bytes --]

      reply	other threads:[~2014-10-13  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 15:06 QT 5.2.1 and eglfs 0x3003 error Yannick Calmettes
2014-10-10 15:16 ` Eric Bénard
2014-10-13  7:20   ` Yannick Calmettes [this message]

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=543B7D3B.6030108@analogway.com \
    --to=yannick.calmettes@analogway.com \
    --cc=eric@eukrea.com \
    --cc=meta-freescale@yoctoproject.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 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.