All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ann Thornton <Ann.Thornton@freescale.com>
To: <meta-freescale@yoctoproject.org>
Subject: Re: BSP Packagegroup
Date: Thu, 9 Jul 2015 11:29:15 -0500	[thread overview]
Message-ID: <559EA15B.2060606@freescale.com> (raw)
In-Reply-To: <CA+jg_OV9U6e0aq27FJwjxFzYqRnk65+zcuw_R467PvMpdZpuJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]


For packagegroup divisions, how about
graphics
multimedia
networking
tools
(probably others I haven't thought of)

Each of those groups might be further divided into minimal, core, demos, 
extended as needed.

Each packagegroup could check DISTRO-FEATURES, etc so that they would be 
as generic as possible.

Then recipes could include the level of detail desired and they would 
work across product lines.

Ann Thornton

On 7/9/2015 9:56 AM, Daiane Angolini wrote:
> For me, packagegroup is only a set of packages wrapped together to
> make my life easier.
>
> Should BSP provide packagegroups to ease the addition (and removal) of
> set o BSP packages, or their “functional” dependency. For example an
> application such as aplay is needed to stress the audio functionality,
> even though there is no dependency from alsa driver from kernel with
> alsa-utils. Should BSP provide packagegroups?
>
> I think offering packagegroup options to enable BSP pieces may really
> ease the BSP usage, however I main point here is how far should BSP
> go. What is the limit between a BSP packagegroup and a "demo"
> packagegroup (as we does in meta-fsl-demos)?
>
> Thinking about a package group to provide BSP packages related with
> VPU, in my opinion it should have:
>
> * VPU firmware
> * VPU lib
>
> In case I’m using gstreamer, I would like a packagegroup like:
>
> * VPU firmware
> * VPU lib
> * gstreamer plugins for VPU (gstreamer-imx or gst1.0-fsl-plugin)
>
> In case I’m using gstreamer with kernel mainline:
>
> * VPU firmware
> * gstreamer
>
>
> Should mp3 encoder (such as lame) be part of a BSP packagegroup? And
> in GPU case? Would DEPENDS and PROVIDES be enough to include needed
> packages?
>
> Should meta-fsl-arm (or meta-freescale) provide a bluetooth BSP
> packagegroup even though there is no special hardware acceleration
> provided by meta-fsl-arm for bluetooth?
>
>
> Daiane


-- 
Ann Thornton

/Microcontrollers Software and Applications
Freescale Semiconductors
email: Ann.Thornton@freescale.com/

[-- Attachment #2: Type: text/html, Size: 2777 bytes --]

  reply	other threads:[~2015-07-09 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 14:56 BSP Packagegroup Daiane Angolini
2015-07-09 16:29 ` Ann Thornton [this message]
2015-07-11 14:24   ` Daiane Angolini
2015-07-15 16:21     ` Ann Thornton
2015-07-15 16:29       ` Daiane Angolini
2015-07-15 16:49         ` Otavio Salvador

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=559EA15B.2060606@freescale.com \
    --to=ann.thornton@freescale.com \
    --cc=meta-freescale@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.