All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: qemu opengl issues
Date: Fri, 17 Aug 2012 16:31:17 +0100	[thread overview]
Message-ID: <502E63C5.3010205@communistcode.co.uk> (raw)
In-Reply-To: <1345216456.27428.13.camel@ted>


>>
>> Right, this is a known limitation - see Yocto Project bug 2407. By pure
>> coincidence I was thinking about fixing it today as I am testing some other
>> related changes; for now the only options are install the required recipes or
>> hack out the gl-requiring parts of the qemu recipe.
>
> I think we're about at the point where we're going to remove GL pass
> through support and drop our qemu GL patches. Patches will likely appear
> next week.
>
> Cheers,
>
> Richard
>

Sounds good, I'm on holiday from the 22nd till 29th so will hopefully 
see them when I get back!

Apologies for not checking the bug tracker first.

*side note: with so many categories it can be a massive farse trying to 
navigate the bugzilla to find bugs, even more so on top of an already 
cluttered/complicated web application.

edit: I have just looked to see if I could find the bug without looking 
at it first (using the id) and I failed miserably.. maybe the force is 
not with my today but I couldn't even decipher where qemu issues would be.

Regards,

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2012-08-17 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 14:54 qemu opengl issues Jack Mitchell
2012-08-17 15:00 ` Paul Eggleton
2012-08-17 15:14   ` Richard Purdie
2012-08-17 15:31     ` Jack Mitchell [this message]
2012-08-17 15:34       ` Paul Eggleton

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=502E63C5.3010205@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.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.