All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: meta-baryon flexibility
Date: Wed, 18 Jul 2012 08:55:35 -0700	[thread overview]
Message-ID: <5006DC77.8080600@linux.intel.com> (raw)
In-Reply-To: <CANFv2Emy5u12VVOWdJHkPSzm6JqoKBBi9Fbd_9MZnLOS7r8t9g@mail.gmail.com>

On 18/07/12 04:40, James Abernathy wrote:
> On Tue, Jul 17, 2012 at 6:19 PM, Joshua Lock <josh@linux.intel.com
> <mailto:josh@linux.intel.com>> wrote:
>
>
>     On Tue, 2012-07-17 at 15:24 -0400, Jim Abernathy wrote:
>      > In an effort to explore how independent a layer could be to the
>      > underlying hardware, I took the meta-baryon NAS layer and got it
>     built
>      > from master using the n450 BSP.  With that working I decided to
>     replace
>      > the n450 with sugarbay.  While the n450 can support X11 and sato,
>     it was
>      > not generated by design in the baryon build.
>      >
>      > However, when I changed to sugarbay, the build stops because X11 is
>      > needed.  To get around this I had to comment out some things in the
>      > conf/machine/sugarbay.conf file in the BSP.
>      >
>      >
>      > #XSERVER ?= "${XSERVER_IA32_BASE} \
>      > #           ${XSERVER_IA32_EXT} \
>      > #           ${XSERVER_IA32_I965} \
>      > #           "
>      >
>      > #VA_FEATURES ?= "gst-va-intel va-intel"
>      >
>      > #MACHINE_EXTRA_RRECOMMENDS += "${VA_FEATURES}"
>      >
>      > Why didn't I have to do this in the n450??
>
>     The key piece is the MACHINE_EXTRA_RRECOMMENDS, which is telling Poky to
>     recommend the gst-va-intel and va-intel recipes when building this
>     machine.
>
>     RRECOMMENDS are automatically installed as a dependency (in this case,
>     of task-machine-base, see task-base.bbclass) but can be removed without
>     causing the package which pulled it in to be removed (see the Poky
>     reference manual glossary on *_RRECOMMENDS).
>
>     http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html
>
>     I'd suggest the RRECOMMENDS actually be added at a more granular level
>     than the machine. Perhaps you could file a bug against the BSP?
>
> So if I understand this, it would be better for one of the image.bb
> <http://image.bb> files that focused on media to include this particular
> RRECOMMENDS statement.  That way others not interested in media and
> graphic could still use the BSP unchanged.

Arguably, yes. But (devil's advocate) what about image recipes which 
aren't part of the core? i.e. if you've been using a different board to 
develop a custom image and then switch to using the sugarbay wouldn't 
you want the accelerated video to "just work"?

I'd suggest a possible solution would be to define an opt-in 
IMAGE_FEATURES[1][2] for multimedia which the sugarbay BSP can add these 
recipes to.

Joshua

1. 
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#var-IMAGE_FEATURES
2. 
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-features-image
-- 
Joshua Lock
         Yocto Project
         Intel Open Source Technology Centre


      reply	other threads:[~2012-07-18 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 19:24 meta-baryon flexibility Jim Abernathy
2012-07-17 22:19 ` Joshua Lock
2012-07-18 11:40   ` James Abernathy
2012-07-18 15:55     ` Joshua Lock [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=5006DC77.8080600@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=jfabernathy@gmail.com \
    --cc=yocto@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.