From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: ml@communistcode.co.uk, openembedded-core@lists.openembedded.org
Subject: Re: qemu opengl issues
Date: Fri, 17 Aug 2012 16:34:09 +0100 [thread overview]
Message-ID: <6117437.nEeZ99LCxr@helios> (raw)
In-Reply-To: <502E63C5.3010205@communistcode.co.uk>
On Friday 17 August 2012 16:31:17 Jack Mitchell wrote:
> Richard Purdie wrote:
> > On Fri, 2012-08-17 at 16:00 +0100, Paul Eggleton wrote:
> >> 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.
>
> 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.
No worries - it's nice when people do check first but I wouldn't personally
consider it mandatory.
> *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.
I usually just do a keyword search using the box at the top - seems effective
to me most of the time.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-08-17 15:46 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
2012-08-17 15:34 ` Paul Eggleton [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=6117437.nEeZ99LCxr@helios \
--to=paul.eggleton@linux.intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox