From: Philip Balister <philip@balister.org>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Updates to mesa and llvm
Date: Mon, 26 Oct 2015 14:46:16 -0700 [thread overview]
Message-ID: <562E9F28.3070508@balister.org> (raw)
Recently I need to get the llvmpipe driver running with mesa. I ended up
adding a llvm-3.7 recipe and updating mesa to 10.6.8. Not sure if going
to 11.x.y also works.
I'd like to upstream these since they configuration actually worked and
performance was much better. I recall some discussion lately about this
process and wanted to make sure I didn't break anything :)
I'll send on the llvm 3.7 stuff this week, since it should work in
parallel with the older recipe. I do need to move the license file
checksum into the version specific piece.
The timing on the mesa update is trickier since we are trying to
stabilize the oe-core release.
Comments? Will adding another llvm recipe cause trouble for other packages?
Philip
next reply other threads:[~2015-10-26 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 21:46 Philip Balister [this message]
2015-10-26 21:59 ` Updates to mesa and llvm Nicolas Dechesne
2015-10-26 22:08 ` Philip Balister
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=562E9F28.3070508@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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