From: "Carlos Rafael Giani" <crg7475@mailbox.org>
To: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] mesa no longer supports swrast starting with version 21
Date: Tue, 13 Apr 2021 16:59:35 +0200 [thread overview]
Message-ID: <0e7b70ec-5231-5215-3d48-46757bb1c161@mailbox.org> (raw)
In-Reply-To: <DBBPR04MB7753B8396CF64FD49321E994E24F9@DBBPR04MB7753.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Ah, right. I'm still not that used to going to Github for meta-freescale
issues :)
On 13.04.21 16:44, Tom Hochstein wrote:
>> -----Original Message-----
>> From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Carlos Rafael Giani via lists.yoctoproject.org
>>
>> Did anybody already look into this? According to the article, swrast was replaced
>> with llvmpipe. It is not clear to me why swrast was ever used,
>> however:
>>
>> # For parts with GPU and DRM, use osmesa, dri, and swrast
>> PACKAGECONFIG_REMOVE_NXPBSP_imxgpu_imxdrm = "gallium"
>> PACKAGECONFIG_APPEND_NXPBSP_imxgpu_imxdrm = "osmesa"
>> DRIDRIVERS_NXPBSP_imxgpu_imxdrm = "swrast"
>>
>> Why did this need swrast for using DRM?
> It seems these changes originated here [1] to fix a build issue. See [2].
>
> [1] https://github.com/Freescale/meta-freescale/commit/3b0fc734634f8f0db1f48fc13c64cacd3d99dd92
> [2] https://github.com/Freescale/meta-freescale/issues/699
>
>
>
[-- Attachment #2: Type: text/html, Size: 2094 bytes --]
prev parent reply other threads:[~2021-04-13 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 13:57 mesa no longer supports swrast starting with version 21 Carlos Rafael Giani
2021-04-13 14:44 ` [meta-freescale] " Tom Hochstein
2021-04-13 14:59 ` Carlos Rafael Giani [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=0e7b70ec-5231-5215-3d48-46757bb1c161@mailbox.org \
--to=crg7475@mailbox.org \
--cc=meta-freescale@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).