All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Sapp, Randolph" <rs@ti.com>
Cc: afd@ti.com, denys@ti.com, reatmon@ti.com, detheridge@ti.com,
	meta-ti@lists.yoctoproject.org, k-bhargav@ti.com
Subject: Re: [EXTERNAL] Re: [meta-ti] [kirkstone PATCH 1/4] meta-ti-bsp: mesa: Add current patches
Date: Thu, 26 Jan 2023 18:02:09 -0500	[thread overview]
Message-ID: <20230126230209.GF22689@denix.org> (raw)
In-Reply-To: <WU64PR.Z83RZ7R0JR5O1@ti.com>

On Thu, Jan 26, 2023 at 04:37:44PM -0600, Sapp, Randolph wrote:
> On Thu, Jan 26 2023 at 03:48:04 PM -0500, Denys Dmytriyenko
> <denis@denix.org> wrote:
> >On Thu, Jan 26, 2023 at 11:06:17AM -0600, Andrew Davis via
> >lists.yoctoproject.org wrote:
> >> On 1/25/23 9:08 PM, Randolph Sapp wrote:
> >> >Copy over current patches from oe-core for mesa since we're
> >>going to be
> >> >overriding the SRC_URI string and we still need those.
> >> >
> >>
> >> We control the repo we will be pointing at, I'd say just add these
> >> patches over there directly so this commit would be not needed.
> >
> >No, these are upstream mesa patches, not the one needed for pvr.
> >
> >Hence, you don't need to carry them locally, since you don't copy
> >the entire
> >upstream mesa recipe.
> 
> Ah, but we do need to carry them since we clobber the mesa SRC_URI
> to load our new source. Now, yes, these should probably be carried
> in our mesa branch instead of in meta-ti. I'll adjust that.

No, not really.

In mesa*.bbappend you include the pvr-meda.inc, which has this SRC_URI:

+SRC_URI = "git://gitlab.freedesktop.org/StaticRocket/mesa.git;protocol=https;branch=${BRANCH} \
+           file://0001-meson.build-check-for-all-linux-host_os-combinations.patch \
+           file://0002-meson.build-make-TLS-ELF-optional.patch \
+           file://0001-meson-misdetects-64bit-atomics-on-mips-clang.patch \
+           file://0001-futex.h-Define-__NR_futex-if-it-does-not-exist.patch \
+           file://0001-util-format-Check-for-NEON-before-using-it.patch \
+           file://0001-Revert-egl-wayland-deprecate-drm_handle_format-and-d.patch \
+           "

So, specifically:

1. No, you don't need to carry patches locally when they are already alongside 
the original .bb recipe, when you are doing a .bbappend

2. You don't need to merge them to your own tree, as long as you specify them 
in the SRC_URI list, when using a .bbappend

-- 
Denys


  reply	other threads:[~2023-01-26 23:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  3:08 [kirkstone PATCH 0/4] Graphics, graphics, and more graphics Randolph Sapp
2023-01-26  3:08 ` [kirkstone PATCH 1/4] meta-ti-bsp: mesa: Add current patches Randolph Sapp
2023-01-26 17:06   ` Andrew Davis
2023-01-26 20:48     ` [meta-ti] " Denys Dmytriyenko
2023-01-26 22:37       ` [EXTERNAL] " Sapp, Randolph
2023-01-26 23:02         ` Denys Dmytriyenko [this message]
2023-01-26 23:45           ` [EXTERNAL] " Sapp, Randolph
2023-01-26  3:08 ` [kirkstone PATCH 2/4] meta-ti-bsp: graphics: Resolve dependency chain Randolph Sapp
2023-01-26 17:54   ` Andrew Davis
2023-01-26 19:38     ` Sapp, Randolph
2023-01-26 20:12       ` Andrew Davis
2023-01-26 22:40         ` Sapp, Randolph
2023-01-26  3:08 ` [kirkstone PATCH 3/4] meta-ti-bsp: machine: Remove all gpu features Randolph Sapp
2023-01-26 18:02   ` Andrew Davis
2023-01-26 21:38     ` Ryan Eatmon
2023-01-26  3:08 ` [kirkstone PATCH 4/4] meta-ti-bsp: machine: Attempt to update DC alias Randolph Sapp
2023-01-26 18:07   ` Andrew Davis
2023-01-26 18:13 ` [kirkstone PATCH 0/4] Graphics, graphics, and more graphics Andrew Davis
2023-01-26 20:46   ` [meta-ti] " Denys Dmytriyenko

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=20230126230209.GF22689@denix.org \
    --to=denis@denix.org \
    --cc=afd@ti.com \
    --cc=denys@ti.com \
    --cc=detheridge@ti.com \
    --cc=k-bhargav@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    --cc=rs@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.