From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to force mesa3d to use llvmpipe?
Date: Fri, 22 Dec 2017 22:52:35 +0100 [thread overview]
Message-ID: <7829580e-0ae9-e063-5124-c4e2cde424da@gmail.com> (raw)
In-Reply-To: <1513977748342-0.post@n4.nabble.com>
Hi Nimai,
Le 22/12/2017 ? 22:22, nimaim a ?crit?:
> Looks like BR may still not have llvmpipe support. Curious if this patch got
> anywhere?
> http://lists.busybox.net/pipermail/buildroot/2017-July/195823.html
This patch series is still present in the patchwork [1] but this work need to be
updated with the latest llvm/clang release (5.0.1).
However, you can still test this series and you should be able to use llvmpipe.
I have not announced it yet on the mailing list that there will be a student at
Smile working on this subject. He will present his internship topic during the
next Buildroot meeting [2].
Enabling llvmpipe support in mesa is not really difficult but packaging
llvm/clang is a more difficult and time consuming task.
You're welcome to work on this series and give some feedback.
Best regards,
Romain
[1] http://patchwork.ozlabs.org/bundle/kubu/llvm-clang
[2] https://elinux.org/Buildroot:DeveloperDaysFOSDEM2018#Meeting_agenda
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2017-12-22 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 20:53 [Buildroot] How to force mesa3d to use llvmpipe? nimaim
2017-12-22 21:22 ` nimaim
2017-12-22 21:52 ` Romain Naour [this message]
2017-12-22 22:10 ` Nimai Mahajan
2017-12-22 23:08 ` Adrian Perez de Castro
2017-12-22 23:11 ` Adrian Perez de Castro
2017-12-23 0:05 ` Nimai Mahajan
2017-12-24 16:46 ` Nimai Mahajan
2017-12-25 12:08 ` Romain Naour
2017-12-26 14:00 ` Nimai Mahajan
2017-12-22 23:50 ` Nimai Mahajan
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=7829580e-0ae9-e063-5124-c4e2cde424da@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@busybox.net \
/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.