All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denys@ti.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][master][PATCH 2/3] Move Graphics and Multimedia drivers and apps out of recipes-bsp
Date: Fri, 31 Jan 2020 14:56:12 -0500	[thread overview]
Message-ID: <20200131195611.GG23242@beryl> (raw)
In-Reply-To: <f871b691-2d2e-6d3c-4210-0e49b004a476@ti.com>

On Fri, Jan 31, 2020 at 02:39:52PM -0500, Andrew F. Davis wrote:
> On 1/31/20 2:33 PM, Denys Dmytriyenko wrote:
> > On Fri, Jan 31, 2020 at 02:21:10PM -0500, Andrew F. Davis wrote:
> >> recipes-bsp is looking a bit random at the moment, lets move graphics
> >> recipies into recipes-graphics and some multimedia related ones into
> >> recipes-multimedia.
> > 
> > Yeah, let me sit on this one for a bit - I'm slightly torn here, as I like 
> > some of the new names/locations, but not all them...
> > 
> 
> 
> Same, I wasn't sure if I even wanted to post this one, but some later
> work I did depended on the new locations and I didn't feel like un-doing it.
> 
> Anyway here is another thing I was thinking:
> 
> recipes-bsp -> firmwares
> recipes-kernel -> all kernel stuff including kernel modules
> recipes-graphics -> just the UM side drivers and apps
> 
> Right now we have kernel module recipes in several places, usually
> bundled either their assosiated firmware or UM drivers. If we split
> things out like above we can keep everything in more consistent locations.
> 
> Let me know if you have a prefrence either way.

I've been noticing that recipes-bsp has been growing out of proportion.

Some old names are historic, but maybe even more correct, e.g.:
https://en.wikipedia.org/wiki/PowerVR

I like "vivante" rename. Still thinking about "img" vs. powervr due to above.

Historically, out-of-tree kernel modules lived in recipes-bsp, while 
user-space apps and libs in recipes-graphics/recipes-multimedia. But I 
might agree to moving drivers away from recipes-bsp to leave that only 
for firmwares and maybe LLDs...

Denys


> 
> Andrew
> 
> 
> > 
> >> Signed-off-by: Andrew F. Davis <afd@ti.com>
> >> ---
> >>  .../{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb        | 0
> >>  .../ti-img-rogue-driver/0001-km-support-general-toolchain.patch   | 0
> >>  .../ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb             | 0
> >>  .../{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb | 0
> >>  ...001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 0
> >>  .../ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb                     | 0
> >>  .../{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb         | 0
> >>  .../ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb                | 0
> >>  .../{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb       | 0
> >>  .../ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb            | 0
> >>  .../ti-img-encode-decode/viddec-test-app_1.0.0.bb                 | 0
> >>  .../ti-img-encode-decode/videnc-test-app_1.0.0.bb                 | 0
> >>  12 files changed, 0 insertions(+), 0 deletions(-)
> >>  rename recipes-bsp/{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb (100%)
> >>  rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver/0001-km-support-general-toolchain.patch (100%)
> >>  rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb (100%)
> >>  rename recipes-graphics/{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb (100%)
> >>  rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch (100%)
> >>  rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb (100%)
> >>  rename recipes-graphics/{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb (100%)
> >>  rename {recipes-bsp/gc320-drivers => recipes-graphics/ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb (100%)
> >>  rename recipes-graphics/{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb (100%)
> >>  rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb (100%)
> >>  rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/viddec-test-app_1.0.0.bb (100%)
> >>  rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/videnc-test-app_1.0.0.bb (100%)
> >>
> >> diff --git a/recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb b/recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb
> >> similarity index 100%
> >> rename from recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb
> >> rename to recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb
> >> diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch b/recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch
> >> similarity index 100%
> >> rename from recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch
> >> rename to recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch
> >> diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb b/recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb
> >> similarity index 100%
> >> rename from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> >> rename to recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb
> >> diff --git a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb b/recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb
> >> similarity index 100%
> >> rename from recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb
> >> rename to recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb
> >> diff --git a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch b/recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch
> >> similarity index 100%
> >> rename from recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch
> >> rename to recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch
> >> diff --git a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb b/recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb
> >> similarity index 100%
> >> rename from recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
> >> rename to recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb
> >> diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb b/recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb
> >> similarity index 100%
> >> rename from recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >> rename to recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb
> >> diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb b/recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb
> >> similarity index 100%
> >> rename from recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> >> rename to recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb
> >> diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb b/recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb
> >> similarity index 100%
> >> rename from recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
> >> rename to recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb
> >> diff --git a/recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb b/recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb
> >> similarity index 100%
> >> rename from recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb
> >> rename to recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb
> >> diff --git a/recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb b/recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb
> >> similarity index 100%
> >> rename from recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb
> >> rename to recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb
> >> diff --git a/recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb b/recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb
> >> similarity index 100%
> >> rename from recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb
> >> rename to recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb
> >> -- 
> >> 2.17.1
> >>

  reply	other threads:[~2020-01-31 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 19:21 [meta-ti][master][PATCH 1/3] conf/machine: use xz over gz for images Andrew F. Davis
2020-01-31 19:21 ` [meta-ti][master][PATCH 2/3] Move Graphics and Multimedia drivers and apps out of recipes-bsp Andrew F. Davis
2020-01-31 19:33   ` Denys Dmytriyenko
2020-01-31 19:39     ` Andrew F. Davis
2020-01-31 19:56       ` Denys Dmytriyenko [this message]
2020-01-31 20:12         ` Andrew F. Davis
2020-01-31 19:21 ` [meta-ti][master][PATCH 3/3] recipes-graphics: Use M for kernel build subdirectory over SUBDIRS Andrew F. Davis
2020-01-31 19:37   ` Denys Dmytriyenko
2020-01-31 19:47     ` Andrew F. Davis
2020-01-31 19:29 ` [meta-ti][master][PATCH 1/3] conf/machine: use xz over gz for images Denys Dmytriyenko
2020-01-31 19:32   ` Andrew F. Davis

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=20200131195611.GG23242@beryl \
    --to=denys@ti.com \
    --cc=afd@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    /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.