All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ahsan, Noor" <Noor_Ahsan@mentor.com>
To: sujith h <sujith.h@gmail.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto][meta-qt5] How to increase depth of qemuarm	from bootargs?
Date: Mon, 18 Apr 2016 11:18:53 +0000	[thread overview]
Message-ID: <365E1805BC95084CBE82381A0B8699940127D10813@EU-MBX-01.mgc.mentorg.com> (raw)
In-Reply-To: <CADyYWL=A4MiQO8Vi+AGD397=kKVzULFTW0fr6c_WnUG_9O=Zkg@mail.gmail.com>

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

Hello Guys,

Nay help on this one. We tried qemux86 and egl examples are working fine on qemux86. The difference is it is using VMware vga driver. We were not able to change the driver on qemuarm.

Noor

From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of sujith h
Sent: Friday, April 15, 2016 12:49 PM
To: OE-core
Subject: [OE-core] Fwd: [yocto][meta-qt5] How to increase depth of qemuarm from bootargs?


---------- Forwarded message ----------
From: sujith h <sujith.h@gmail.com<mailto:sujith.h@gmail.com>>
Date: Thu, Apr 14, 2016 at 2:53 PM
Subject: [yocto][meta-qt5] How to increase depth of qemuarm from bootargs?
To: "yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>" <yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>>
Cc: Noor_Ahsan@mentor.com<mailto:Noor_Ahsan@mentor.com>

Hi all,
I am trying to build Qt5 from meta-qt5 ( master branch ) with poky( machine is qemuarm). The qtbase is built successfully and is installed into core-image-sato. When I run : runqemu qemuarm
I can see the matchbox window launched successfully.The qtbase is having gles2 enabled in the PACKAGECONFIG and gl is removed from PACKAGECONFIG. In mesa I have enabled gallium. I do see a problem when I try to run qtbase opengl examples.The gui gets displayed. But the image(s) associated with it never displays. For example lets say there is an example known as cube. When I try to run cube ( with -platform xcb), I could see a black screen. The cube image never comes. So my query is if it's possible to increase the depth ( default used is 16 for qemuarm ) to 24 through bootargs? If so a helping hand would be great. Let me know if more information is required regarding my setup. I have poky + meta-qt5 + meta-oe + meta-ruby layers in bblayers.conf.
Thanks,
Sujith H

--
സുജിത് ഹരിദാസന്
Bangalore
<Project>Contributor to KDE project
<Project>Contributor to Yocto project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
<Blog> http://sujithh.info
C-x C-c



--
സുജിത് ഹരിദാസന്
Bangalore
<Project>Contributor to KDE project
<Project>Contributor to Yocto project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
<Blog> http://sujithh.info
C-x C-c

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

  reply	other threads:[~2016-04-18 11:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  9:23 [meta-qt5] How to increase depth of qemuarm from bootargs? sujith h
2016-04-15  7:48 ` [yocto][meta-qt5] " sujith h
2016-04-18 11:18   ` Ahsan, Noor [this message]
2016-04-15  7:50 ` sujith h

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=365E1805BC95084CBE82381A0B8699940127D10813@EU-MBX-01.mgc.mentorg.com \
    --to=noor_ahsan@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sujith.h@gmail.com \
    /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.