From: Randolph Sapp <rs@ti.com>
To: Andrew Davis <afd@ti.com>, Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][scarthgap][RFC 6/6] mesa-pvr: Use mesa-pvr for all TI SoCs
Date: Wed, 17 Sep 2025 13:22:58 -0500 [thread overview]
Message-ID: <DCVA9O56NNYP.3LRTIEDU4CVL2@ti.com> (raw)
In-Reply-To: <3bb49aca-f4b6-4205-baec-51f556e5bb0c@ti.com>
On Fri Sep 12, 2025 at 11:38 AM CDT, Andrew Davis wrote:
> On 9/9/25 3:52 PM, Randolph Sapp wrote:
>> On Tue Sep 9, 2025 at 10:10 AM CDT, Andrew Davis wrote:
>>> TI SoCs without GPUs can still use mesa-pvr as it will simply fallback to
>>> SW rendering just like the normal mesa package. The benefit is using the
>>> same version across all supported devices is more consistent and only
>>> one version of Mesa is needed for all TI SoCs.
>>>
>>> Signed-off-by: Andrew Davis <afd@ti.com>
>>> ---
>>
>> [snip]
>>
>> Originally this was done to mitigate damage in the event where there is an
>> issue with mesa. I'm not entirely sure we want to move everything over to
>> pvr-mesa as they still hijack some of the common dri code for their own goofy
>> stuff.
>>
>
> Fair point, would be nice if the PVR support didn't touch the core/common DRI
> at all. Having this the common Mesa for all boards would help in identifying
> if they broke anything in the common/sw rendering side though, right now we
> would only find those bugs if one was both using a device with GPU *and* it
> falls back to SW.
>
>> My opinion is we should use vanilla software where we can. Especially
>> considering we'll need to be able to access vanilla mesa for AM62 later if I get
>> my way.
>>
>
> Could you expand on that? Outside of the eventual switch to the upstream
> PVR driver, what would we need vanilla mesa for on AM62?
>
> Andrew
Ah, not much to expand on really. Upstream driver needs vanilla mesa, and I'd
like to avoid shipping hacked libraries on devices that don't need em.
- Randolph
next prev parent reply other threads:[~2025-09-17 18:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 15:10 [meta-ti][scarthgap][RFC 1/6] ti-sgx-ddk-um: UM side driver depends on KM side driver Andrew Davis
2025-09-09 15:10 ` [meta-ti][scarthgap][RFC 2/6] ti-bsp: Do not remove gpu MACHINE_FEATURE conditionally on BSP version Andrew Davis
2025-09-09 20:44 ` Denys Dmytriyenko
2025-09-12 16:31 ` Andrew Davis
2025-09-12 18:24 ` Denys Dmytriyenko
2025-09-17 21:54 ` Andrew Davis
2025-09-17 21:57 ` Randolph Sapp
2025-09-09 15:10 ` [meta-ti][scarthgap][RFC 3/6] ti-bsp: Use same version for both UM and KM driver Andrew Davis
2025-09-09 20:42 ` Ryan Eatmon
2025-09-12 16:28 ` Andrew Davis
2025-09-09 15:10 ` [meta-ti][scarthgap][RFC 4/6] mesa-pvr: Remove need for PVR/SGX display aliases Andrew Davis
2025-09-09 15:10 ` [meta-ti][scarthgap][RFC 5/6] mesa-pvr: Use PREFERRED_PROVIDER directly for GPU selection Andrew Davis
2025-09-09 15:10 ` [meta-ti][scarthgap][RFC 6/6] mesa-pvr: Use mesa-pvr for all TI SoCs Andrew Davis
2025-09-09 20:52 ` Randolph Sapp
2025-09-12 16:38 ` Andrew Davis
2025-09-17 18:22 ` Randolph Sapp [this message]
2025-09-17 18:40 ` Andrew Davis
2025-09-17 19:12 ` Randolph Sapp
2025-09-17 19:15 ` Andrew Davis
2025-09-17 19:36 ` Randolph Sapp
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=DCVA9O56NNYP.3LRTIEDU4CVL2@ti.com \
--to=rs@ti.com \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/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.