All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Ankur Tyagi <Ankur.Tyagi@gallagher.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [Thud branch][AM3354]OpenGL/QT font rendering problem - corrupt glyphs
Date: Wed, 19 Feb 2020 18:52:06 -0500	[thread overview]
Message-ID: <20200219235206.GX720@beryl> (raw)
In-Reply-To: <SY2PR01MB24265CF57E3A14572D8434B7E5100@SY2PR01MB2426.ausprd01.prod.outlook.com>

That is quite strange. We are wrapping up our Thud support. But it was used 
in our products for about a year with rigorous testing and we haven't seen 
anything like that on any of our platforms.

This does look like some memory corruption - are you sure you have all the 
timings correctly? Have you also switched any of the low-level components, 
like U-boot, Linux kernel, etc.?

Denys


On Wed, Feb 19, 2020 at 07:04:12PM +0000, Ankur Tyagi wrote:
> Hi,
> 
> Is there anything can be done to fix it? Let me know if some more information needs to be shared in order to help with diagnosis.
> 
> Regards
> Ankur
> 
> 
> ________________________________
> From: meta-arago-bounces@arago-project.org <meta-arago-bounces@arago-project.org> on behalf of Ankur Tyagi <Ankur.Tyagi@gallagher.com>
> Sent: Tuesday, February 18, 2020, 11:11 AM
> To: meta-arago@arago-project.org
> Subject: [meta-arago] [Thud branch][AM3354]OpenGL/QT font rendering problem - corrupt glyphs
> 
> Resending it as previous one didn’t made it to the mailing list
> 
> And we are stuck in production after upgrade to thud branch because of this issue, any help is appreciated
> 
> Regards
> Ankur
> 
> From: Ankur Tyagi
> Sent: Tuesday, 11 February 2020 12:39 PM
> To: meta-arago@arago-project.org
> Subject: [Thud branch][AM3354]OpenGL/QT font rendering problem - corrupt glyphs
> 
> Greetings,
> 
> I am using AM3354 processor. I just did a major Yocto upgrade from "daisy" to "thud" branch, and I noticed that some characters/glyphs happen to be slightly corrupt.
> The problem occurs randomly, but when a corrupted character is rendered multiple times on the screen, all of its instances are corrupted the same way.
> 
> It looks like this: https://ibb.co/LYP4JCx
> 
> I tried using various QT environment variables, but the only one that worked was QT_QUICK_BACKEND=software. However, this led to a very significant slowdown, so it's not an option.
> 
> I'm not using X11 or wayland. I'm not modifying the graphics drivers or the QT layer in any way.
> 
> Following are Qt environment variables on target:
> 
> export QT_QPA_EGLFS_INTEGRATION=none
> export QT_QUICK_CONTROLS_1_STYLE=Flat
> export QT_QPA_EGLFS_NO_LIBINPUT=1
> 
> Has anyone experienced similar problem? Is there any configuration detail I might be missing?
> 
> Regards,
> Ankur
> 
> ________________________________
> This email is confidential and may contain information subject to legal privilege. If you are not the intended recipient please advise us of our error by return e-mail then delete this email and any attached files. You may not copy, disclose or use the contents in any way. The views expressed in this email may not be those of Gallagher Group Ltd or subsidiary companies thereof.
> ________________________________
> 

> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago



  reply	other threads:[~2020-02-19 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MEAPR01MB2567716832C5FA4F6E472CF2E5190@MEAPR01MB2567.ausprd01.prod.outlook.com>
2020-02-17 22:10 ` [Thud branch][AM3354]OpenGL/QT font rendering problem - corrupt glyphs Ankur Tyagi
2020-02-19 19:04   ` Ankur Tyagi
2020-02-19 23:52     ` Denys Dmytriyenko [this message]
2020-02-20  8:32       ` Ankur Tyagi
2020-02-27  4:58       ` Ondrej Pohl

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=20200219235206.GX720@beryl \
    --to=denys@ti.com \
    --cc=Ankur.Tyagi@gallagher.com \
    --cc=meta-arago@arago-project.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.