From: richard.purdie@linuxfoundation.org
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: kernel@pengutronix.de, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] mesa: make gallium swrast target optional
Date: Fri, 14 Jun 2019 14:26:29 +0100 [thread overview]
Message-ID: <c85e93b13ddcbc27c27ac17fdcf97a0d1ffc4020.camel@linuxfoundation.org> (raw)
In-Reply-To: <99B005A2-CD21-4AA8-B960-54121098F850@gmail.com>
On Fri, 2019-06-14 at 15:05 +0200, Alexander Kanavin wrote:
> I guess the patch needs a small tweak so that swrast remains enabled,
> but becomes optional. Then Marco can set packageconfig exactly as he
> wants.
I guess if we can track down where the swrast dependency is coming and
and change things to avoid it, that would probably be ok.
I tend to think swrast is in a better state that it is in reality :(.
> The second patch is fine as it is, I think. Only qemu implements
> virgl device at the moment.
The second patch should be fine, I had to drop it as it depends on the
first though.
Cheers,
Richard
next prev parent reply other threads:[~2019-06-14 13:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 17:54 [PATCH 1/2] mesa: make gallium swrast target optional Marco Felsch
2019-06-13 17:54 ` [PATCH 2/2] mesa: make gallium virgl " Marco Felsch
2019-06-13 18:17 ` [PATCH 1/2] mesa: make gallium swrast " Martin Jansa
2019-06-13 18:38 ` Marco Felsch
2019-06-13 19:07 ` Martin Jansa
2019-06-14 10:55 ` Richard Purdie
2019-06-14 12:04 ` Marco Felsch
2019-06-14 12:11 ` richard.purdie
2019-06-14 12:34 ` Marco Felsch
2019-06-14 12:45 ` Alexander Kanavin
2019-06-14 13:16 ` Burton, Ross
2019-06-14 13:31 ` Alexander Kanavin
2019-06-14 12:50 ` richard.purdie
2019-06-14 13:05 ` Alexander Kanavin
2019-06-14 13:26 ` richard.purdie [this message]
2019-06-14 13:33 ` Alexander Kanavin
2019-06-14 13:36 ` Burton, Ross
2019-06-14 13:37 ` Alexander Kanavin
2019-06-17 9:35 ` Marco Felsch
2019-06-17 11:21 ` Alexander Kanavin
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=c85e93b13ddcbc27c27ac17fdcf97a0d1ffc4020.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=kernel@pengutronix.de \
--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