From: "Sapp, Randolph" <rs@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Andrew Davis <afd@ti.com>, <reatmon@ti.com>, <denys@ti.com>,
<detheridge@ti.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] Re: [meta-ti] [master][PATCH v2] meta-ti-bsp: Graphics recipe overhaul
Date: Wed, 21 Dec 2022 10:49:19 -0600 [thread overview]
Message-ID: <7Q29NR.T2R7VR8YUI2B2@ti.com> (raw)
In-Reply-To: <20221219213235.GX22689@denix.org>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Mon, Dec 19 2022 at 16:32:35 -05:00:00, Denys Dmytriyenko
<denis@denix.org> wrote:
> Can you please explain why existing machine feature cannot be re-used
> and a
> new one is needed here? Do you plan to use both side-by-side?
Yes, so gpu is a super generic machine feature. On our platforms this
could mean anything from some minimal device with a tidss module that
wants to do software rendering to a full blown device with rogue/sgx
graphics processors. The gpu feature is required to build graphics
libraries in either case, but if they are doing software rendering they
won't need the rogue/sgx specific patches. The new machine feature
makes this distinction clear and allows us to switch between
rogue/sgx/swrast tooling as necessary.
[-- Attachment #2: Type: text/html, Size: 913 bytes --]
next prev parent reply other threads:[~2022-12-21 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 17:45 [master][PATCH v2] meta-ti-bsp: Graphics recipe overhaul Randolph Sapp
2022-12-07 17:15 ` Ryan Eatmon
2022-12-07 18:48 ` [meta-ti] " Andrew Davis
2022-12-09 22:18 ` Sapp, Randolph
2022-12-14 0:07 ` Denys Dmytriyenko
2022-12-14 18:47 ` Andrew Davis
2022-12-14 20:26 ` Sapp, Randolph
2022-12-19 21:32 ` Denys Dmytriyenko
2022-12-21 16:49 ` Sapp, Randolph [this message]
2022-12-22 22:47 ` [EXTERNAL] " Denys Dmytriyenko
2022-12-27 18:36 ` [EXTERNAL] " Sapp, Randolph
2023-01-04 23:07 ` Denys Dmytriyenko
2023-01-11 19:33 ` Sapp, Randolph
2023-01-11 19:37 ` Andrew Davis
2022-12-14 18:03 ` Sapp, Randolph
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=7Q29NR.T2R7VR8YUI2B2@ti.com \
--to=rs@ti.com \
--cc=afd@ti.com \
--cc=denis@denix.org \
--cc=denys@ti.com \
--cc=detheridge@ti.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.