All of lore.kernel.org
 help / color / mirror / Atom feed
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, 11 Jan 2023 13:33:07 -0600	[thread overview]
Message-ID: <7B6COR.0OP8M9KYKL9S3@ti.com> (raw)
In-Reply-To: <20230104230752.GO22689@denix.org>

On Wed, Jan 4 2023 at 06:07:52 PM -0500, Denys Dmytriyenko 
<denis@denix.org> wrote:
> Please list all the machine features you plan to add/rename/remove in
> order to support all these use cases. Thanks.

On further inspection I believe adding these as distro features may be 
a better idea than machine features.

I believe the best course of action would be to re-evaluate all recipes 
that utilize the "gpu" machine feature and either switch it to use 
distro features and PACKAGECONFIGS (my gstreamer-plugins example should 
actually be removed as it is a pointless override).

Either x11 or wayland distro features should be enough to pull in 
software rendering toolkits and graphics frameworks like Qt so any 
overrides we had to prevent that should be dropped. That seems to be 
the way upstream intends that to work.

The rgx-gpu / sgx-gpu features will be added to switch mesa configs, 
pull in according kernel modules, and tweak other packages as 
necessary. There will need to be a preliminary check though to make 
sure sgx-gpu and rgx-gpu features aren't both included as currently 
these will clash.

Please feel free to correct me though. Unfortunately Yocto gives us too 
much freedom here.

Regards,
Randolph Sapp




  reply	other threads:[~2023-01-11 19:33 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           ` [EXTERNAL] " Sapp, Randolph
2022-12-22 22:47             ` Denys Dmytriyenko
2022-12-27 18:36               ` [EXTERNAL] " Sapp, Randolph
2023-01-04 23:07                 ` Denys Dmytriyenko
2023-01-11 19:33                   ` Sapp, Randolph [this message]
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=7B6COR.0OP8M9KYKL9S3@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.