All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sapp, Randolph" <rs@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: <denys@ti.com>, <reatmon@ti.com>, <detheridge@ti.com>,
	<meta-arago@lists.yoctoproject.org>, <k-bhargav@ti.com>
Subject: Re: [meta-arago] [master/kirkstone][PATCH] all: Graphics recipe overhaul
Date: Fri, 20 Jan 2023 13:03:59 -0600	[thread overview]
Message-ID: <NYSSOR.ZG32SG9FGUKC@ti.com> (raw)
In-Reply-To: <09c8b020-ed7d-0bb0-6c6b-adcd23388397@ti.com>

On Fri, Jan 20 2023 at 11:42:11 AM -0600, Andrew Davis <afd@ti.com> 
wrote:
> This should be MACHINE_FEATURES and be moved out of meta-arago and 
> down
> into the meta-ti layer where we define the mainline kernel if we can.

Ha, you haven't seen the full notes on my other patch have you?
https://lists.yoctoproject.org/g/meta-ti/topic/96386295#15613

I switched these to be COMBINED_FEATURES. Like alsa, they require both 
a machine feature and a distro feature to be present to actually patch 
the packages we need. In this way patches become opt-in and software 
rendering becomes the default unless someone specifically wants a 
distro with powervr-rogue-graphics patches.

In addition if they have a distro that wants powervr-rogue-graphics and 
they are compiling for a machine that doesn't have that feature then it 
will also fall back to software rendering.

The only issue this doesn't solve is when someone wants to hack recipes 
like gstreamer to introduce pseudo graphics support or bundle random 
pieces of the graphics stack without including all of it, but arguably 
that should be a specialized package group or new layer anyway.




      reply	other threads:[~2023-01-20 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 20:42 [master/kirkstone][PATCH] all: Graphics recipe overhaul Randolph Sapp
2023-01-20 17:42 ` [meta-arago] " Andrew Davis
2023-01-20 19:03   ` Sapp, Randolph [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=NYSSOR.ZG32SG9FGUKC@ti.com \
    --to=rs@ti.com \
    --cc=afd@ti.com \
    --cc=denys@ti.com \
    --cc=detheridge@ti.com \
    --cc=k-bhargav@ti.com \
    --cc=meta-arago@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.